AGENT SKILL

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
所属仓库
boarlabsxyz/skills
最近更新
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

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.md and 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 -v and .git/config: is this a GitHub repo? Which one?
  • AGENTS.md and CLAUDE.md at the repo root: does either exist, and is either a symlink (ls -l)? Is there already an ## Agent skills section in either?
  • GLOSSARY.md and GLOSSARY-MAP.md at the repo root
  • docs/adr/ and any src/*/docs/adr/ directories
  • docs/agents/: does this skill's prior output already exist?
  • Is the mpc_triage skill installed? (a mpc_triage skill folder alongside this one, or mpc_triage in 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 the gh CLI. boar_review and boar_codex read tickets with gh, 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 where gh label list shows an existing label that plainly plays one of these roles under another name (e.g. bug:triage for needs-triage) use that label instead, so mpc_triage applies it rather than creating a duplicate. Skip labels altogether when mpc_triage isn't installed.
  • Domain docs: single-context (one GLOSSARY.md + docs/adr/ at the repo root). Use multi-context (a root GLOSSARY-MAP.md pointing to per-context GLOSSARY.md files) only when the repo already has a GLOSSARY-MAP.md.
  • Agent file: CLAUDE.md holds the ## Agent skills block, and AGENTS.md is 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.md with the block, then ln -s CLAUDE.md AGENTS.md.
  • Only CLAUDE.md exists: edit it, then ln -s CLAUDE.md AGENTS.md.
  • Only AGENTS.md exists, as a regular file: rename it (git mv AGENTS.md CLAUDE.md when it is tracked, else mv), edit it, then ln -s CLAUDE.md AGENTS.md.
  • AGENTS.md is already a symlink to CLAUDE.md: edit CLAUDE.md.
  • Both are regular files with the same content: replace AGENTS.md with the symlink and edit CLAUDE.md.
  • Both are regular files that differ: edit CLAUDE.md and leave AGENTS.md untouched; in the report, say that AGENTS.md is a separate file that Codex reads instead of CLAUDE.md, and that merging it into CLAUDE.md and replacing it with the symlink would give every agent one text.
  • CLAUDE.md is a symlink to AGENTS.md: the two are already one file; edit it through CLAUDE.md and 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:

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