fission-ai__openspec/openspec/changes/fix-opencode-commands-directory/specs/command-generation/spec.md at codex/warp-skills-320

mirror of https://github.com/Fission-AI/OpenSpec.git synced 2026-09-14 20:16:53 +08:00

Files

T

Fabián Silva 61eb999f7c fix(opencode): use plural commands/ directory to match OpenCode convention (#760 )

* fix(opencode): use plural `commands/` directory to match OpenCode convention

The OpenCode adapter was using `.opencode/command/` (singular) but OpenCode's
official documentation specifies `.opencode/commands/` (plural). This aligns
with every other adapter in the codebase. Legacy cleanup updated to detect
old singular-path artifacts. Fixes #748.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(legacy): detect both opsx-* and openspec-* patterns, auto-cleanup in CI

- Extend LegacySlashCommandPattern.pattern to accept string | string[]
- OpenCode legacy entry now detects both opsx-*.md and openspec-*.md
- Auto-cleanup legacy artifacts in non-interactive mode instead of
  aborting with exit 1 (safe: slash commands are OpenSpec-managed,
  config cleanup only removes markers)
- Add 7 tests (6 legacy detection + 1 non-interactive init)
- Update spec with array pattern support and auto-cleanup scenario

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* chore: update task description to reflect dual-pattern support

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Tabish Bidiwale <30385142+TabishB@users.noreply.github.com>

2026-02-27 00:08:22 -08:00

3.2 KiB

Raw Permalink Blame History

MODIFIED Requirements

Requirement: ToolCommandAdapter interface

The system SHALL define a ToolCommandAdapter interface for per-tool formatting.

Scenario: Adapter interface structure

WHEN implementing a tool adapter
THEN ToolCommandAdapter SHALL require:
- toolId: string identifier matching AIToolOption.value
- getFilePath(commandId: string): returns file path for command (relative from project root, or absolute for global-scoped tools like Codex)
- formatFile(content: CommandContent): returns complete file content with frontmatter

Scenario: Claude adapter formatting

WHEN formatting a command for Claude Code
THEN the adapter SHALL output YAML frontmatter with name, description, category, tags fields
AND file path SHALL follow pattern .claude/commands/opsx/<id>.md

Scenario: Cursor adapter formatting

WHEN formatting a command for Cursor
THEN the adapter SHALL output YAML frontmatter with name as /opsx-<id>, id, category, description fields
AND file path SHALL follow pattern .cursor/commands/opsx-<id>.md

Scenario: Windsurf adapter formatting

WHEN formatting a command for Windsurf
THEN the adapter SHALL output YAML frontmatter with name, description, category, tags fields
AND file path SHALL follow pattern .windsurf/workflows/opsx-<id>.md

Scenario: OpenCode adapter formatting

WHEN formatting a command for OpenCode
THEN the adapter SHALL output YAML frontmatter with description field
AND file path SHALL follow pattern .opencode/commands/opsx-<id>.md using path.join('.opencode', 'commands', ...) for cross-platform compatibility
AND the adapter SHALL transform colon-based command references (/opsx:name) to hyphen-based (/opsx-name) in the body

ADDED Requirements

Requirement: Legacy cleanup for renamed OpenCode command directory

The legacy cleanup module SHALL detect and remove old OpenCode command files from the previous singular .opencode/command/ directory path.

Scenario: Detect old singular-path OpenCode command files

WHEN running legacy artifact detection on a project with files matching .opencode/command/opsx-*.md or .opencode/command/openspec-*.md
THEN the system SHALL include those files in the legacy slash command files list via LEGACY_SLASH_COMMAND_PATHS
AND LegacySlashCommandPattern.pattern SHALL accept string | string[] to support multiple glob patterns per tool

Scenario: Clean up old OpenCode command files on init

WHEN a user runs openspec init in a project with old .opencode/command/ artifacts
THEN the system SHALL remove the old files
AND generate new command files at .opencode/commands/

Scenario: Auto-cleanup legacy artifacts in non-interactive mode

WHEN a user runs openspec init in non-interactive mode (e.g., CI) and legacy artifacts are detected
THEN the system SHALL auto-cleanup legacy artifacts without requiring --force
AND legacy slash command files (100% OpenSpec-managed) SHALL be removed
AND config file cleanup SHALL only remove OpenSpec markers (never delete user files)

3.2 KiB Raw Permalink Blame History