/setup-matt-pocock-skills 技能

它的作用

setup-matt-pocock-skills answers three questions about one repo: where issues live, what the triage labels are called, and where the domain docs sit. It records the answers as markdown files under docs/agents/.

Those files are the only thing that varies between repos. The skills themselves are identical everywhere. They read docs/agents/issue-tracker.md at run time and do what it says. That is why the set is not tied to GitHub, and why you never edit a skill file to point it at another tracker. Invoking it with "link the skills to a custom issue tracker" works with anything you can connect to programmatically, with no changes to the skills.

它是一个提示词驱动的技能，不是确定性的脚本。它读取你的 git remote, CLAUDE.md and GLOSSARY.md, proposes what it found, and waits for you to confirm before it writes anything.

何时使用

你通过输入 /setup-matt-pocock-skills; the agent won't reach for it on its own. Its metadata marks it non-invokable on purpose, so no other skill can fire it for you.

每个仓库使用一次，在任何其他工程技能首次使用之前。如果 triage, to-spec, to-tickets or wayfinder start guessing where your issues go, or apply labels your tracker doesn't have, this repo has not been set up yet. You can run it in a repo halfway through a project. The skill reads what is already there, so no earlier work is lost.

前置条件

它写入你运行它的仓库：

You commit all of it as markdown. There is no user-level or global mode. The config lives in the repo, so every repo gets its own copy.

三个决策

It starts each section with the recommended answer, and skips any question its exploration already answered. Most runs need only two confirmations.

追踪器选项：

The first three ship as templates in the skill and work out of the box. Local markdown is a full option, not a fallback. The skill supports a solo project with no remote. One caveat: don't use local markdown if you use GitHub. They are alternatives, so pick one.

"Other" is a full option too. It is how Jira, Linear, Azure DevOps and Beads all work. You describe the workflow, the skill records your prose in docs/agents/issue-tracker.md, and the downstream skills follow the prose. Users have already built this: a Jira-over-MCP 变体，一个形似 gh，一个手工搭建的本地看板。

常见问题

我必须使用 GitHub 吗？

不。GitHub、GitLab 和 .scratch/ all ship as ready-made templates, and anything else works through the "other" path. This is the most-repeated question, in roughly these words: 「硬锁定到 github」, 「我可以用 GitLab / Jira 吗」, 「那 Azure DevOps 呢」. The answer is always the same: setup chooses the tracker, not the skill.

更新技能后我需要重跑它吗？

The direct answer after v1.1 was yes. The skill's own closing message is softer. It tells you to re-run only to switch trackers or start over. Both are defensible. The seed templates change between versions, so a docs/agents/issue-tracker.md from an older release can go out of date against the skills that now read it. If a downstream skill does something different from what the docs describe, re-run setup. It is cheap.

它写入了 CLAUDE.md，但我用的是 Codex。

This is a known gap, and still open. The file-selection rule is "edit CLAUDE.md 如果存在，否则 AGENTS.md". It checks which file exists, not which 运行框架 is running. In a repo with a CLAUDE.md left over from Claude Code, the skill writes its ## Agent skills block to a file Codex never reads. Users have two workarounds: move the block to AGENTS.md 手动，或者保持 AGENTS.md 标准，并让 CLAUDE.md a one-line pointer at it. If neither file exists, the skill asks you which to create instead of picking one. This has confused people who expected it to decide.

它没有创建我的分流标签。

它不会。 docs/agents/triage-labels.md 是一个 mapping: it tells /triage 你的追踪器中哪些字符串对应五个标准角色。它不会运行 gh label create. On a fresh GitHub repo the labels do not exist yet, and users have filed this as a bug more than once. Two consequences:

• 如果你的追踪器已经使用标准名称，映射就是一张恒等表，无需配置任何东西。这是预期的常见情况，不是缺失的步骤。
• This skill does not create wayfinder的 wayfinder:map and wayfinder:<type> labels either, and gh issue create --label <missing> fails instead of creating the label. Create them by hand before the first wayfinder run on a GitHub repo.

Can I configure the other skills' behaviour here (追问审视 cadence, question format, tone)?

No. It configures three things: tracker, labels, doc layout. Users have asked to make it the place for per-user preferences. The answer is that skills stay opinionated and take no per-user config. Preferences belong in your CLAUDE.md 作为纯文本指令，每个技能都已经在读取。

我能把配置保存在 ~/.claude 而不是把它提交到每个仓库？

Not today. A user who runs the skills across many repos has an open request for this, but no user-level mode exists. Every repo carries its own docs/agents/.

让一个技能配置其他技能，不奇怪吗？

一个长期存在的抱怨说是的，原话如下： "having a skill to set up the other skill does not feel right to me: that means the LLM is configuring its own skills." The trade-off is real. Without a setup step, every skill that touches issues would need its own copy of the tracker instructions. The output is markdown you can read and edit, and that limits the risk. You can read every file it wrote and change it by hand. Make day-to-day changes that way, not with another run.

做到以下就算成功

• docs/agents/issue-tracker.md and docs/agents/domain.md 存在，加上 triage-labels.md if triage 已安装。
• 一个 ## Agent skills section appears in the instruction file your harness reads, with a one-line summary pointing at each of those files.
• The tracker it proposed matches the remote you use, and the label strings match labels that exist in your tracker.
• 之后， /to-tickets 发布时不问你在哪里管 issue，而 /triage 应用现有标签，而不是发明标签。
• 技能文件本身没有任何改变。如果配置修改了 SKILL.md，出问题了。

在流程中的位置

setup-matt-pocock-skills 是 一次性的配置 对于工程流程来说，它是其他一切的前提假设，而不是链上的一步。它的邻居就是它的读者： triage，它应用了这里写下的标签词汇； to-spec and to-tickets，它们发布到此处指定的追踪器；而 wayfinder, which reads the "Wayfinding operations" section of the same tracker file to learn how to store maps and child tickets. domain-modeling later fills in the domain-doc layout that setup records. It creates GLOSSARY.md and ADRs only when you resolve a term or decision, so a repo with no domain docs after setup is normal. For which skill to reach for next, ask-matt 路由整个技能集。