setup-repo-skills
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain do
SKILL.mdskills/setup-repo-skills/SKILL.md
GitHubSetup Matt Pocock's Skills
Scaffold the per-repo configuration that the engineering skills assume:
- Issue tracker — where issues live (GitHub by default; local markdown is also supported out of the box)
- Triage labels — the strings used for the five canonical triage roles
- Domain docs — where
CONTEXT.mdand ADRs live, and the consumer rules for reading them
This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
Process
1. Explore
Look at the current repo to understand its starting state. Read whatever exists; don't assume:
Read sections/explore-checklist.md for what to look at.
2. Present findings and ask
Summarise what's present and what's missing. Then walk the user through the three decisions one at a time — present a section, get the user's answer, then move to the next. Don't dump all three at once.
Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.
Section A — Issue tracker.
Read sections/issue-tracker.md.
Section B — Triage label vocabulary.
Read sections/triage-labels.md.
Section C — Domain docs.
Read sections/domain-docs.md.
3. Confirm and edit
Show the user a draft of:
- The
## Agent skillsblock to add to whichever ofCLAUDE.md/AGENTS.mdis being edited (see step 4 for selection rules) - The contents of
docs/agents/issue-tracker.md,docs/agents/triage-labels.md,docs/agents/domain.md
Let them edit before writing.
4. Write
Read sections/file-selection.md to pick which file to edit.
Read sections/agent-skills-block.md for the block to write.
Then write the three docs files using the seed templates in this skill folder as a starting point:
- issue-tracker-github.md — GitHub issue tracker
- issue-tracker-gitlab.md — GitLab issue tracker
- issue-tracker-local.md — local-markdown issue tracker
- triage-labels.md — label mapping
- domain.md — domain doc consumer rules + layout
For "other" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.
5. Done
Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit docs/agents/*.md directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.
Sections
Read a section only when its condition applies; do not preload them.
- sections/explore-checklist.md: read when exploring the repo (step 1)
- sections/issue-tracker.md: read when presenting Section A (issue tracker)
- sections/triage-labels.md: read when presenting Section B (triage labels)
- sections/domain-docs.md: read when presenting Section C (domain docs)
- sections/file-selection.md: read when choosing which file to write the block into (step 4)
- sections/agent-skills-block.md: read when writing the
## Agent skillsblock (step 4)