Use skill descriptions as Claude adapter preview text

[sebastientaggart]

Summary

• Replace the generic "You are executing the /X skill. Your argument is: $ARGUMENTS" header in the Claude adapter with each skill's description from frontmatter
• Fix the release skill description to avoid an unresolved {{BRANCH_PROD}} template variable that would render as a literal in previews

Before:

/start    You are executing the `/start` skill. Your argument is: $ARGUMENTS
/ship     You are executing the `/ship` skill. Your argument is: $ARGUMENTS

After:

/start    Start a new feature or bugfix
/ship     Type-check, commit, open PR, review, and merge to the integration branch

Issue #11

Test plan

• Run ./sync.sh --force and verify all .claude/commands/*.md files have descriptive first lines
• Verify skill previews display correctly in Claude CLI (/ to list commands)
• Confirm $ARGUMENTS still works in skill bodies that reference it

🤖 Generated with Claude Code

[sebastientaggart]

Code Review

Scope: adapters/claude/header.md, skills/release.md, all generated .claude/commands/*.md files

Correctness

• {description} in the header is resolved by build_header() via fm.get('description', skill_name). All skills have a description field.
• review-agent sets no_invocation_header: true, so unaffected.
• $ARGUMENTS is referenced in skill bodies, not the header — removing it from the header breaks nothing.
• The release.md description fix is correct: build_header() does not run apply_placeholders(), so {{BRANCH_PROD}} would have rendered as a literal.

Regressions

None identified.

Suggestions (non-blocking)

• SUGGESTION: The old header reminded the model about $ARGUMENTS. Skills that use it document this in their body, so not a functional issue — just a trade-off.
• SUGGESTION: The release description could say "promote the pre-production branch to the production branch" for slightly more consistent language with the body.

Verdict

APPROVE — correct, no regressions, fixes a pre-existing bug (unresolved {{BRANCH_PROD}}).