SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillssetup-matt-pocock-skills

setup-matt-pocock-skills

Agents & models

View repository

Updated 10-16 01:38

About this skill

Setup Matt Pocock's Skills

Set up the per-repo configuration that the engineering skills assume:

Scaffold the per-repo configuration that the engineering skills assume:

  • Issue tracker — where issues live (defaults to GitHub; local markdown is also supported out of the box)

    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

    The strings used for the five canonical triage roles

  • Domain docs — CONTEXT.md and where ADRs live, plus the consumption rules for reading them

    Where CONTEXT.md and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, present findings, confirm with the user, then write.

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 initial state. Read what already exists; do not assume:

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?

    git remote -v and .git/config — is this a GitHub repo? Which one?

  • Repo root AGENTS.md and CLAUDE.md — do they exist? Do they already contain a ## Agent skills section?

    AGENTS.md and CLAUDE.md at the repo root — does either exist? Is there already an ## Agent skills section in either?

  • Repo root CONTEXT.md and CONTEXT-MAP.md

    CONTEXT.md and CONTEXT-MAP.md at the repo root

  • docs/adr/ and any src/*/docs/adr/ directories

    docs/adr/ and any src/*/docs/adr/ directories

  • docs/agents/ — does prior output from this skill already exist?

    docs/agents/ — does this skill's prior output already exist?

  • .scratch/ — a sign that a local markdown issue tracker convention is already in use

    .scratch/ — sign that a local-markdown issue tracker convention is already in use

2. Present findings and ask

Summarize what exists and what is missing. Thenone at a timewalk the user through three decisions — present one section, get the user's answer, then move to the next. Do not dump all three at once.

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. Start each section with a brief explanation (what it is, why these skills need it, what changes if a different choice is made). Then show the choices and defaults.

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。

Explainer: the "issue tracker" is where issues live for this repo. Skills like to-issues、triage、to-prd and qa read from and write to it — they need to know whether to call gh issue create, write markdown files under .scratch/ , or follow some other workflow you describe. Choose where you actually track work for this repo. The "issue tracker" is where issues live for this repo. Skills like to-issues, triage, to-prd, and qa read from and write to it — they need to know whether to call gh issue create, write a markdown file under .scratch/, or follow some other workflow you describe. Pick the place you actually track work for this repo.

Default stance: these skills are designed for GitHub. If git remote points to GitHub, propose that. If git remote points to GitLab (gitlab.com or self-hosted), propose GitLab. Otherwise (or if the user prefers), offer:

Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:

  • GitHub — issues live in the repo's GitHub Issues (using gh CLI）

    Issues live in the repo's GitHub Issues (uses the gh CLI)

  • GitLab — issues live in the repo's GitLab Issues (using glab CLI）

    Issues live in the repo's GitLab Issues (uses the glab CLI)

  • Local markdown — issues live as files under this repo's .scratch/<feature>/ (good for personal projects or repos with no remote)

    Issues live as files under .scratch/<feature>/ in this repo (good for solo projects or repos without a remote)

  • Other(Jira, Linear, etc.) — have the user describe the workflow in a paragraph; the skill records it as free text

    Ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose

Section B — Triage label vocabulary。

Explainer: When the triage skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to claim, ready for human handling, or won't fix. To do this, it needs to apply labels (or the equivalent in your issue tracker) that match youractual configuration'sstrings. If your repository already uses different label names (for example bug:triage instead of needs-triage), map them here so the skill applies the correct labels instead of creating duplicates. When the triage skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings you've actually configured. If your repo already uses different label names (e.g. bug:triage instead of needs-triage), map them here so the skill applies the right ones instead of creating duplicates.

Five canonical roles:

The five canonical roles:

  • needs-triage — maintainer needs to evaluate
  • needs-info — waiting on reporter for more information
  • ready-for-agent — fully specified, AFK-ready (an agent can pick it up with no human context)
  • ready-for-human — needs human implementation
  • wontfix — will not be actioned

Default: each role's string equals its name. Ask the user whether they want to override. If their issue tracker has no existing labels, the defaults are fine.

Default: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.

Section C — Domain docs。

Explainer: Some skills (improve-codebase-architecture、diagnose、tdd) read the CONTEXT.md file to learn the project's domain language, and docs/adr/ to learn about past architecture decisions. They need to know whether the repository has one global context or multiple (for example a monorepo with separate frontend/backend contexts), so they look in the right place. Some skills (improve-codebase-architecture, diagnose, tdd) read a CONTEXT.md file to learn the project's domain language, and docs/adr/ for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend/backend contexts) so they look in the right place.

Confirm the layout:

Confirm the layout:

  • Single context — one at the repository root CONTEXT.md + docs/adr/. Most repositories are this.

    One CONTEXT.md + docs/adr/ at the repo root. Most repos are this.

  • Multi-context — root CONTEXT-MAP.md points to each context's CONTEXT.md file (usually a monorepo).

    CONTEXT-MAP.md at the root pointing to per-context CONTEXT.md files (typically a monorepo).

3. Confirm and edit

Show the user a draft of the following:

Show the user a draft of:

  • The CLAUDE.md / AGENTS.md block to add to the ## Agent skills being edited (see step 4 for selection rules)

    The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)

  • docs/agents/issue-tracker.md、docs/agents/triage-labels.md、docs/agents/domain.md contents

    The contents of docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md

Let the user edit before writing.

Let them edit before writing.

4. Write

Choose the file to edit:

Pick the file to edit:

  • If CLAUDE.md exists, edit it.

    If CLAUDE.md exists, edit it.

  • Otherwise if AGENTS.md exists, edit it.

    Else if AGENTS.md exists, edit it.

  • If neither exists, ask the user which one to create — do not choose for them.

    If neither exists, ask the user which one to create — don't pick for them.

When CLAUDE.md already exists, never create AGENTS.md(and vice versa) — always edit the one that already exists.

Never create AGENTS.md when CLAUDE.md already exists (or vice versa) — always edit the one that's already there.

If the selected file already has a ## Agent skills block, update its contents in place instead of appending a duplicate. Do not overwrite the user's edits in surrounding sections.

If an ## Agent skills block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.

That block:

The block:

## Agent skills

### Issue tracker

[issue 跟踪位置的一行摘要]。见 `docs/agents/issue-tracker.md`。
[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.

### Triage labels

[标签词汇的一行摘要]。见 `docs/agents/triage-labels.md`。
[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.

### Domain docs

[布局的一行摘要——"单上下文"或"多上下文"]。见 `docs/agents/domain.md`。
[one-line summary of layout — "single-context" or "multi-context"]. See `docs/agents/domain.md`.

Then write the three documentation files using the seed templates in this skill folder as a starting point:

Then write the three docs files using the seed templates in this skill folder as a starting point:

For "other" issue trackers, write from scratch using the user's description docs/agents/issue-tracker.md。

For "other" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.

5. Done

Tell the user that setup is complete, and which engineering skills will now read from these files. Mention that they can edit directly afterward docs/agents/*.md— they only need to rerun this skill if they want to switch issue trackers or start from scratch.

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.