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-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- 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 资源文件 6
- 参考文档agents/openai.yaml152 B
- 参考文档domain.md2.0 KB
- 参考文档issue-tracker-github.md3.7 KB
- 参考文档issue-tracker-gitlab.md3.7 KB
- 参考文档issue-tracker-local.md1.8 KB
- 参考文档triage-labels.md1.0 KB
03 SKILL.md 正文
Setup Matt Pocock's Skills
Scaffold per-repo config the engineering skills assume:
- Issue tracker — where issues live (GitHub by default; local markdown also supported)
- Triage labels — strings for the five canonical triage roles
- Domain docs — where
CONTEXT.mdand ADRs live, plus consumer rules for reading them
Prompt-driven, not a deterministic script. Explore, present findings, confirm with user, then write.
Process
1. Explore
Inspect current repo state. Read what exists; don't assume:
git remote -vand.git/config— GitHub repo? Which one?AGENTS.mdandCLAUDE.mdat repo root — either exist? Already an## Agent skillssection in either?CONTEXT.mdandCONTEXT-MAP.mdat repo rootdocs/adr/and anysrc/*/docs/adr/dirsdocs/agents/— this skill's prior output already there?.scratch/— sign a local-markdown issue tracker convention is in use- Is
triageskill installed? (atriageskill folder alongside this one, ortriagein available skills.) Decides whether Section B runs. - Monorepo signals —
pnpm-workspace.yaml, aworkspacesfield inpackage.json, or populatedpackages/*with ownsrc/. Present only in a genuinely large multi-package repo; absence means single-context, almost every repo.
2. Present findings and ask
Summarise present vs missing. Take sections in order — one section, one answer, then next.
Lead each section with recommended answer so user accepts in a word. One-line explainer only when choice genuinely branches; skip section when exploration settled it (Section B when triage not installed, Section C when no monorepo).
Section A — Issue tracker.
Explainer: The "issue tracker" is where issues live for this repo. Skills like
to-tickets,triage, andto-specread/write it — they need to know whether to callgh issue create, write a markdown file under.scratch/, or follow another workflow you describe. Pick where you actually track work.
Default posture: designed for GitHub. If a git remote points at GitHub, propose that. If at GitLab (gitlab.com or self-hosted), propose GitLab. Otherwise (or if user prefers), offer:
- GitHub — issues in repo's GitHub Issues (uses
ghCLI) - GitLab — issues in repo's GitLab Issues (uses
glabCLI) - Local markdown — issues as files under
.scratch/<feature>/(good for solo projects or repos without a remote) - Other (Jira, Linear, etc.) — ask user to describe workflow in one paragraph; recorded as freeform prose
Record choice in docs/agents/issue-tracker.md. GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted off — leave it off and don't raise it; user can flip the flag in the file later.
Section B — Triage label vocabulary. Skip entirely if triage skill not installed — an uninstalled skill needs no labels.
If installed, ask exactly one question:
Keep default triage labels? (recommended: yes)
Defaults are the five canonical roles, each label string equal to its name: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. On yes, write as-is. Only if user says no — usually because their tracker uses other names (e.g. bug:triage for needs-triage) — collect overrides so triage applies existing labels instead of creating duplicates.
Section C — Domain docs. Default single-context — one CONTEXT.md + docs/adr/ at repo root. Fits almost every repo; write without asking.
Offer multi-context — a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files — only when exploration found monorepo signals. Then confirm which layout they want.
3. Confirm and edit
Show user a draft of:
- The
## Agent skillsblock to add to whichever ofCLAUDE.md/AGENTS.mdis edited (see step 4 for selection rules) - Contents of
docs/agents/issue-tracker.md,docs/agents/domain.md, anddocs/agents/triage-labels.md(last only whentriageinstalled)
Let them edit before writing.
4. Write
Pick the file to edit:
- If
CLAUDE.mdexists, edit it. - Else if
AGENTS.mdexists, edit it. - If neither exists, ask user which to create — don't pick for them.
Never create AGENTS.md when CLAUDE.md already exists (or vice versa) — always edit the one already there.
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 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 triage installed and Section B ran. Otherwise both omitted.
Then write the 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 (only if
triageinstalled) - 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 user setup is complete and which engineering skills now read these files. Mention they can edit docs/agents/*.md directly later — re-running this skill is only necessary to switch issue trackers or restart from scratch.
04 同仓库更多 Skills
writing-design-docs
Use when the user wants to write a problem-statement design doc, says "let's plan a feature properly" / "write a design doc" / "I'm thinking about how to do X" for a non-trivial X, or before committing to a non-obvious technical direction
write-doc
Use when the user asks to write or draft a README, ADR, runbook, tutorial, how-to, explanation, or reference doc, or a caller passes "type ADR" or "type README". Picks the type, fills a template, adds diagrams. RFCs and design docs belong to writing-design-docs.
review-doc
Use when the user asks to review, critique, score, grade, or "how good is this doc" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.
fix-doc
Use when the user asks to fix, edit for prose quality, polish, tighten, humanize, or de-slop a Markdown doc or pasted text, or says "make this read less AI". Applies review-doc findings, generates flagged diagrams, lists substantive issues for the author, then runs the AI-tell pass last. Modifies the target.
create-slides
Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.
start-session
Open a Claude Code working session in a fresh, isolated git worktree, so the user can start a task with a single /start-session <name>. Use at the START of a session when the user says "start session", "start a worktree", "spin up a worktree for ABC-123", "begin work on <ticket>", or passes a name/ticket to work under. Creates and ENTERS a worktree via the EnterWorktree tool (never `git worktree add`) under .claude/worktrees/, named exactly after the argument, on a local branch `worktree-<argument>`. Reports what the worktree inherited (`.worktreeinclude` copies, symlinked node_modules) and whether its `.env` still points at the main checkout's stack. If the argument is a JIRA key (e.g. ABC-123, PROJ-1505), also loads that story with the Atlassian CLI (`acli`) when available and summarizes the implementation ask. Also renames the session to the argument (the same effect as `/rename <NAME>`) so it's easy to find in `/resume`. Then stops and waits — it sets up the workspace and context, it does not implement.