setup-skills
Installation
SKILL.md
Setup skills
Draft the per-repo documents the ship skill reads, confirming with the human before every write. This skill does only what its parent, setup-matt-pocock-skills, leaves undone and ship needs: it takes the parent's answers on tracker, triage vocabulary and domain-doc layout as given, and asks only about what the parent left open.
Every document you write here is read by an agent: apply writing-for-agents to its prose.
Process
1. Preconditions: instruct and stop
Check all three before exploring. On any failure print the exact command, then "then rerun /setup-skills", and stop.
- Parent docs.
docs/agents/issue-tracker.md,docs/agents/triage-labels.mdanddocs/agents/domain.mdexist. Else:/setup-matt-pocock-skills. One exception: when the host (step 2) is Azure DevOps andissue-tracker.mdis missing or is the parent's freeform "Other" page, offer to write the vendored issue-tracker-ado.md in its place (confirm first), then continue. The parent ships GitHub, GitLab and local templates only. - Composed skills as derived copies.
.claude/skills/holdscode-review,tdd,codebase-design,writing-for-agents,triage,find-docsandshow-me, each recorded in the repo'sskills-lock.json(the skills CLI writes it at install) with therefits line below pins, the upstream commit the source repo tested. A copy the lock records at anotherref, or none, is off its pin: print its line. A copy present but absent from the lock is hand-maintained: report it as "will be replaced by the derived copy", confirm, then refresh it with the same line. A global copy under~/.claude/skillsleaves this check unmet: a personal skill silently shadows a repo's, so ship's composed skills must live in the repo. Else print: