mpc_setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- mpc_setup-matt-pocock-skills
- description
- Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
02 资源文件 3
- 参考文档domain.md2.0 KB
- 参考文档issue-tracker-github.md4.0 KB
- 参考文档triage-labels.md1.0 KB
03 SKILL.md 正文
Setup Matt Pocock's Skills
Scaffold the per-repo configuration that the engineering skills assume:
- Issue tracker: where issues live (the repository's GitHub Issues)
- Triage labels: the strings used for the five canonical triage roles
- Domain docs: where
GLOSSARY.mdand ADRs live, and the consumer rules for reading them
This is a prompt-driven skill, not a deterministic script. Explore, decide by the presets in step 2, write, then report what you wrote. It asks the user nothing.
Process
1. Explore
Look at the current repo to understand its starting state. Read whatever exists; don't assume:
git remote -vand.git/config: is this a GitHub repo? Which one?AGENTS.mdandCLAUDE.mdat the repo root: does either exist, and is either a symlink (ls -l)? Is there already an## Agent skillssection in either?GLOSSARY.mdandGLOSSARY-MAP.mdat the repo rootdocs/adr/and anysrc/*/docs/adr/directoriesdocs/agents/: does this skill's prior output already exist?- Is the
mpc_triageskill installed? (ampc_triageskill folder alongside this one, ormpc_triagein your available skills.) This decides whether labels are written at all. gh label list: the labels the tracker already has.
2. Decide
Every choice is preset for this plugin; ask the user none of them.
- Issue tracker: the GitHub Issues of the repository's
origin, through theghCLI.boar_reviewandboar_codexread tickets withgh, so no other tracker is offered. The "PRs as a request surface" flag in the template stays off. - Triage labels: the five canonical roles, each label string equal to its name:
needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix. Only wheregh label listshows an existing label that plainly plays one of these roles under another name (e.g.bug:triageforneeds-triage) use that label instead, sompc_triageapplies it rather than creating a duplicate. Skip labels altogether whenmpc_triageisn't installed. - Domain docs: single-context (one
GLOSSARY.md+docs/adr/at the repo root). Use multi-context (a rootGLOSSARY-MAP.mdpointing to per-contextGLOSSARY.mdfiles) only when the repo already has aGLOSSARY-MAP.md. - Agent file:
CLAUDE.mdholds the## Agent skillsblock, andAGENTS.mdis a symlink to it, so Claude, Codex and any other agent read one text.
3. Write
The agent file. Make CLAUDE.md a regular file and AGENTS.md a symlink to it, by the starting state:
- Neither exists: create
CLAUDE.mdwith the block, thenln -s CLAUDE.md AGENTS.md. - Only
CLAUDE.mdexists: edit it, thenln -s CLAUDE.md AGENTS.md. - Only
AGENTS.mdexists, as a regular file: rename it (git mv AGENTS.md CLAUDE.mdwhen it is tracked, elsemv), edit it, thenln -s CLAUDE.md AGENTS.md. AGENTS.mdis already a symlink toCLAUDE.md: editCLAUDE.md.- Both are regular files with the same content: replace
AGENTS.mdwith the symlink and editCLAUDE.md. - Both are regular files that differ: edit
CLAUDE.mdand leaveAGENTS.mduntouched; in the report, say thatAGENTS.mdis a separate file that Codex reads instead ofCLAUDE.md, and that merging it intoCLAUDE.mdand replacing it with the symlink would give every agent one text. CLAUDE.mdis a symlink toAGENTS.md: the two are already one file; edit it throughCLAUDE.mdand leave the link as it is.
If an ## Agent skills block already exists in the file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.
The block:
## Agent skills
### Issue tracker
[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.
### Triage labels
[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.
### Domain docs
[one-line summary of layout: "single-context" or "multi-context"]. See `docs/agents/domain.md`.
Include the ### Triage labels sub-block, and write docs/agents/triage-labels.md, only when mpc_triage is installed. When it isn't, both are omitted.
When labels are written, create each one the tracker lacks (gh label create).
Then write the docs files using the seed templates in this skill folder as a starting point:
- issue-tracker-github.md: GitHub issue tracker
- triage-labels.md: label mapping (only if
mpc_triageis installed) - domain.md: domain doc consumer rules + layout
4. Done
Tell the user the setup is complete: what was written (the agent file and its symlink, docs/agents/*.md, the labels created), and which skills will now read from these files. Mention they can edit docs/agents/*.md directly later; re-running this skill is only necessary to restart from scratch.
04 同仓库更多 Skills
mpc_writing-shape
Writing, exploit: shape raw material into an article, paragraph by paragraph.
mpc_writing-fragments
Writing, explore: mine raw fragments, no structure yet.
mpc_writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
mpc_writing-beats
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
mpc_wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
mpc_wait-what
Stop. That last message did not land: re-pitch it.