setup-skills

/setup-skills

Provisions reusable skills into .claude/skills/<id>/SKILL.md for the project. Sibling of setup-agents — same install model, different artifact type.

Mode Detection

Read .claude/starter-context.json if it exists
  → Exists: use skills_selected + conventions + project.name — skip suggestion step
  → Does not exist (standalone): load catalog → detect context → suggest → confirm

Argument Handling

If a skill id is passed directly (e.g. /setup-skills git-workflow): skip the suggestion step and go straight to that catalog entry.

Step 1 — Context Detection

Context mode (starter-context.json present): install exactly the ids listed in skills_selected — skip the suggestion logic below. If skills_selected is absent or empty, the user declined skills at init; do not re-suggest. The suggestWhen / alwaysInclude evaluation applies to standalone mode only.

Load skills-catalog.json. For each entry, evaluate suggestWhen:

1. files: check whether any listed glob exists in the project root
2. context: if starter-context.json exists, evaluate conditions against its fields
3. alwaysInclude: if true, suggest unconditionally — present first

git-workflow is alwaysInclude: true — every project has git.

For each suggested skill: show preview (with resolved variants from Step 2) → confirm before writing.

Step 2 — Resolve Conventions

The template adapts to the conventions chosen at init. Resolve these values:

Token	Source	Fallback
COMMIT_BLOCK	conventions.commit_format (conventional/none/custom)	conventional
BRANCH_BLOCK	conventions.branch_strategy (gitflow/trunk-based)	trunk-based
PROTECTED_BRANCHES	derived from branch_strategy	from trunk-based
PROJECT_NAME	project.name	"this project"
TEMPLATE_VERSION	catalog entry version	(always present)

Standalone mode (no starter-context.json): ask only the two convention questions before injecting — same wording as init Part 3:

• "Branch strategy (trunk-based / gitflow)?"
• "Commit format (conventional / custom / none)?"