setup-matt-pocock-skills

Configures a repository's issue tracker, triage labels, and domain doc layout for engineering skills.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rockcookies/skills --skill setup-matt-pocock-skills-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/rockcookies/skills/tree/main/skills/mattpocock/setup-matt-pocock-skills
Command: npx skills add https://github.com/rockcookies/skills --skill setup-matt-pocock-skills-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which label vocabulary to use, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other engineering skill reads consistent settings instead of guessing. ## Core Features & Use Cases - Issue tracker setup: Detects the repo's remote and records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or a custom workflow, writing the choice to docs/agents/issue-tracker.md. - Triage label vocabulary: Maps the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to the label strings actually used in the repo's tracker. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) structure and consumer rules in docs/agents/domain.md. - Use Case: After installing the engineering skills into a GitHub repo, run this setup once to generate an Agent skills section in CLAUDE.md or AGENTS.md plus the docs/agents/ configuration files, so triage and ticket skills operate against the right tracker. ## Quick Start Ask the agent to run the setup-matt-pocock-skills setup to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.

Frequently Asked Questions about setup-matt-pocock-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a repo for the Matt Pocock engineering skills?▼

Run the setup-matt-pocock-skills skill once before using the other engineering skills. It explores your repo, asks about your issue tracker, triage labels, and domain docs, then writes configuration files under docs/agents/ and an Agent skills section in CLAUDE.md or AGENTS.md.

Which issue trackers does the setup skill support?▼

It supports GitHub Issues via the gh CLI, GitLab Issues via the glab CLI, and local markdown files under .scratch/ for repos without a remote. Other trackers like Jira or Linear can be recorded as freeform prose describing your workflow.

Does the setup skill work with GitLab instead of GitHub?▼

Yes. If git remote points at GitLab, the skill proposes GitLab and writes docs/agents/issue-tracker.md using the glab CLI conventions, including merge request handling and native blocking links where the tier supports them.

What are the default triage labels the skills use?▼

The five canonical labels are needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. The setup writes them as-is by default, but you can override individual strings to match labels your tracker already uses.

When should I re-run the setup skill?▼

Re-running is only necessary if you want to switch issue trackers or restart the configuration from scratch. For smaller changes, edit the files under docs/agents/ directly, since the skills read them at runtime.

Does the setup skill handle monorepos?▼

Yes. When it detects monorepo signals like pnpm-workspace.yaml or a workspaces field in package.json, it offers a multi-context layout with a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files and context-scoped ADR directories.