feat: add CodeArts Agent skills support

[lovewilling009]

Summary

• Add CodeArts as a supported openspec init tool using the codeartsagent tool ID and .codeartsdoer skills directory.
• Preserve adapterless skills-only behavior by skipping command generation when no CodeArts command adapter exists.
• Update CLI/tool documentation and add coverage for init, detection, and command registry behavior.

Verification

• npx vitest run test/core/init.test.ts -t \"CodeArts\"
• npx vitest run test/core/available-tools.test.ts test/core/shared/tool-detection.test.ts test/core/command-generation/registry.test.ts
• npm run lint (passes with existing warning in src/core/references.ts)
• npm run build
• Manual global package smoke test: openspec init --tools codeartsagent

Summary by CodeRabbit

• New Features

  • Added CodeArts (codeartsagent) as a recognized AI tool.
  • Expanded guidance for CodeArts-style, skill-based /openspec-* invocations.

• Bug Fixes

  • Improved tool detection and initialization for CodeArts as a skills-only tool.
  • Clarified that CodeArts does not generate opsx-* command files.

• Documentation

  • Updated CLI options and command-syntax tables to include CodeArts integration guidance.

• Tests

  • Added unit tests covering CodeArts tool detection, init output, and adapterless behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bed208ee-607f-46d1-a22f-c02506d37aa1

📥 Commits

Reviewing files that changed from the base of the PR and between 9b78b4b and a52b699.

📒 Files selected for processing (1)

• test/core/init.test.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• test/core/init.test.ts

---

📝 Walkthrough

Walkthrough

This PR adds CodeArts (codeartsagent) as a supported AI tool, updates init and registry behavior for a skills-only workflow, and refreshes docs and tests to match its slash-command syntax and lack of command-file adapters.

Changes

CodeArts tool support

Layer / File(s)	Summary
Tool entry and detection src/core/config.ts, test/core/available-tools.test.ts, test/core/shared/tool-detection.test.ts	AI_TOOLS gains CodeArts, and detection tests cover discovery through .codeartsdoer.
Adapterless init and registry behavior test/core/command-generation/registry.test.ts, test/core/init.test.ts	codeartsagent is covered as a skills-only tool with no command adapter, including init output and file creation.
Docs for CodeArts syntax docs/cli.md, docs/commands.md, docs/how-commands-work.md, docs/supported-tools.md, docs/troubleshooting.md	Docs add CodeArts to supported-tool lists, command syntax references, and troubleshooting guidance.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Fission-AI/OpenSpec#1003 — Adds another skills-only tool path with AI_TOOLS and init coverage for adapterless behavior.
• Fission-AI/OpenSpec#853 — Extends the same AI_TOOLS-driven integration and downstream tool detection path with a new tool entry.
• Fission-AI/OpenSpec#288 — Adds a new tool entry and related init/command integration through the shared tool registry.

Suggested reviewers

• TabishB

Poem

A rabbit hopped through CodeArts glade,
With skills and tests and docs well laid.
No opsx files? A twitch of nose—
Just /openspec-* where CodeArts goes.
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding CodeArts Agent skills support.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/core/init.test.ts`:
- Line 211: There is a duplicate const declaration for logCalls in the same test
block, which causes a block-scoped redeclaration error. In init.test.ts, keep
only one logCalls definition and remove the extra duplicate line near the
console.log mock usage so the test file compiles cleanly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 980dbd49-2ed6-43f8-81c5-88c369cc5574

📥 Commits

Reviewing files that changed from the base of the PR and between 737518b and 9b78b4b.

📒 Files selected for processing (10)

• docs/cli.md
• docs/commands.md
• docs/how-commands-work.md
• docs/supported-tools.md
• docs/troubleshooting.md
• src/core/config.ts
• test/core/available-tools.test.ts
• test/core/command-generation/registry.test.ts
• test/core/init.test.ts
• test/core/shared/tool-detection.test.ts

[alfred-openspec]

Reviewed the CodeArts Agent skills-only integration across config, init/update behavior, adapterless command handling, docs, and focused tests. Paths match the public CodeArts skills surface, command generation correctly stays skipped without an adapter, and the added coverage hits the right seams.\n\nOne minor existing UX nit: adapterless tools can still appear in the generic success count as if commands exist before the explicit skipped-commands line clarifies it. Not introduced here and not blocking.