Add Command Code integration to spec-kit

[Angelthebestone]

Summary

Adds Command Code as a first-class built-in integration so Spec Kit can be installed into Command Code with:

specify init my-project --integration command-code

Command Code discovers agent skills from .commandcode/skills/<name>/SKILL.md (project) or ~/.commandcode/skills/ (personal), which matches the speckit-<name>/SKILL.md layout Spec Kit's SkillsIntegration base class generates. Skills are invoked in chat as $speckit-<command> (dollar-prefix chat invocation, like Codex/ZCode).

Changes

• New integration class CommandCodeIntegration (src/specify_cli/integrations/command_code/__init__.py), a SkillsIntegration subclass:
  • Installs skills into .commandcode/skills/
  • requires_cli: True (CLI is cmdc/command-code on PATH; supports -p/--output-format json dispatch)
  • Declared multi-install safe (static, isolated .commandcode/ agent root), so it can coexist with Claude Code, Codex, etc.
• Registry: registered in _register_builtins() (import + _register()) and added to integrations/catalog.json.
• Invocation style: added command-code to DOLLAR_SKILLS_AGENTS so specify init next-steps and hook references render $speckit-*.
• Tests: tests/integrations/test_integration_command_code.py reuses the SkillsIntegrationTests mixin (setup/teardown, file inventory, frontmatter, uninstall round-trip, multi-install) plus a $speckit-* next-steps invocation test; command-code added to ALL_INTEGRATION_KEYS in test_registry.py.
• Docs: README note and docs/reference/integrations.md (supported-agents table + multi-install-safe table).

Verification

• pytest tests/integrations/test_integration_command_code.py — 31 passed
• pytest tests/integrations/test_registry.py — 664 passed (includes multi-install-safe contracts)
• Full tests/integrations suite — all files green (only pre-existing skips/warnings)
• Manual smoke test:

specify init smoke-test-proj --integration command-code --script sh

Produced .commandcode/skills/speckit-{analyze,checklist,clarify,constitution,converge,implement,plan,specify,tasks,taskstoissues}/SKILL.md and next-steps showing $speckit-constitution, $speckit-specify, etc. (no /speckit.constitution).

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Review details

Suppressed comments (6)

tests/integrations/test_integration_command_code.py:47

• These assertions expect an invocation Command Code does not use. Installed skills are invoked from its slash menu, so this should verify /speckit-constitution and reject the dollar form.

        assert result.exit_code == 0
        assert "$speckit-constitution" in result.output
        assert "/speckit.constitution" not in result.output

src/specify_cli/_invocation_style.py:15

• Command Code exposes installed skills as slash commands (/speckit-<name>), not dollar commands. Classifying it here makes init guidance, extension hook references, and inherited CLI dispatch emit an invocation the agent will not recognize. Move it to the slash-skills set instead.

DOLLAR_SKILLS_AGENTS: frozenset[str] = frozenset({"codex", "zcode", "command-code"})

src/specify_cli/integrations/command_code/init.py:5

• This documents the wrong invocation syntax. Command Code lists installed skills in its slash menu and invokes this skill as /speckit-<name>, so the module documentation should not advertise a dollar prefix.

(project) or ``~/.commandcode/skills/`` (personal). Skills are invoked in chat
with ``$speckit-<name>``.

tests/integrations/test_integration_command_code.py:14

• The test description codifies the same incorrect dollar-prefix behavior. Command Code uses slash invocations for installed skills, unlike Codex/ZCode.

This issue also appears on line 45 of the same file.

    """Command Code renders $speckit-* chat invocations (like Codex/ZCode)."""

docs/reference/integrations.md:17

• The supported-agents table advertises the wrong invocation syntax. Command Code exposes installed skills as slash commands, so this entry should show /speckit-<command>.

| [Command Code](https://commandcode.ai/docs)                                          | `command-code`   | Skills-based integration; installs skills into `.commandcode/skills/` and invokes them as `$speckit-<command>` |

README.md:93

• Command Code skills use /speckit-<command>, not the Codex-style dollar prefix. Also, every following quickstart example uses the generic slash-dot form, so this sentence needs to tell Command Code and Codex users how to translate those examples rather than sending them to unrecognized commands.

Launch your coding agent in the project directory. Most agents expose spec-kit as `/speckit.*` slash commands; Codex CLI and Command Code in skills mode use `$speckit-*` instead; GitHub Copilot CLI uses `/agents` to select the agent or address it directly in a prompt.

• Files reviewed: 8/8 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[mnriem]

Please address test & lint errors

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Review details

Suppressed comments (1)

tests/integrations/test_integration_command_code.py:14

• The new test only exercises init next-step rendering. Adding this integration to DOLLAR_SKILLS_AGENTS also controls SkillsIntegration.build_command_invocation() and the $speckit-git-commit guidance injected into generated skills, while the existing regression test at tests/integrations/test_base.py:221 still parametrizes only codex and zcode. Please include command-code there (or add equivalent assertions here) so those runtime/generated-file paths are covered.

class TestCommandCodeInvocation:
    """Command Code renders $speckit-* chat invocations (like Codex/ZCode)."""

• Files reviewed: 12/12 changed files
• Comments generated: 0 new
• Review effort level: Balanced

[mnriem]

Thank you!