Skip to content

feat: unify agent skill integration across Claude Code, Codex, and OpenCode (#131) - #231

Merged
androidand merged 4 commits into
mainfrom
feat/131-unify-agent-skill-integration
Nov 11, 2026
Merged

androidand merged 4 commits into
mainfrom
feat/131-unify-agent-skill-integration

Conversation

@androidand

@androidand androidand commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner
  • One canonical skill with two install targets (--claude-code, --agents); --codex and --opencode are aliases. Adds install-skill --drift, --temp and --rollback.
  • CLAUDE.md imports AGENTS.md; doctor install reports canonical and legacy installs, validates the import, and keeps the openspec dependency check.
  • Site: all feature cards now render (five were silently dropped), overlapping cards merged, a Review theme added, and build.sh fails on an unknown group. A test pins the group list.

Closes #131

…enCode (#131)

- Rewrite CLAUDE.md to use @AGENTS.md import (37→9 lines)
- Add SpecSync Skill section to AGENTS.md
- Refactor installskill.go: two canonical targets (claude-code, agents)
  with --codex/--opencode aliases and deduplication
- Broaden SKILL.md description to cover full lifecycle
- Unify doctor diagnostics: detect canonical + legacy paths,
  validate CLAUDE.md @AGENTS.md imports, report JSON output
- Update site/features.json with agent skill diagnostics feature
spec/release-plan requirement 5 (0-indexed, so the sixth) wrapped its text
so the normative keyword was not where the parser looked. Reordered to lead
with the SHALL, which is better spec style regardless: the requirement now
states the rule before the parenthetical about its deferral.

Verified with a negative control — reverting the wording brings
`requirements.5.text: Requirement must contain SHALL or MUST keyword` back,
so the validator is reading the text this change edits and not something
adjacent.

launch-promotion kept its notes at specs/promotion/spec.md, where the
validator correctly refused them: no delta headers, no scenarios, and
"must"/"either-or" rather than normative language. Moved to
promotion-notes.md in the change root, which is what the validator's own
message advises ("or move non-delta notes outside specs/"). That removes
one of the two errors but not the failure — a change with no delta fails
however its notes are filed, and authoring the delta is a judgement about
what the promotion capability should require, not a mechanical fix.

Opens with 27 passed / 15 failed, from 26/16. The remaining 15 are all
"no deltas at all" and need either authored deltas or archiving, which is
a decision rather than a chore.
… unknown group

Five cards (group review or none) never reached the page. Merge the cards that
said the same thing, add the Review theme, and pin the group list with a test.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying specsync with  Cloudflare Pages  Cloudflare Pages

Latest commit: 32f3dce
Status: ✅  Deploy successful!
Preview URL: https://8955c225.specsync.pages.dev
Branch Preview URL: https://feat-131-unify-agent-skill-i.specsync.pages.dev

View logs

@androidand
androidand merged commit 119b168 into main Nov 11, 2026
2 checks passed
@androidand
androidand deleted the feat/131-unify-agent-skill-integration branch November 11, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unify agent skill integration

1 participant