setup-matt-pocock-skills

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

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill setup-matt-pocock-skills-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/engineering/setup-matt-pocock-skills
Command: npx skills add https://github.com/yersonargotev/packy --skill setup-matt-pocock-skills-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where a repo's issues live, which triage label vocabulary to use, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so the other skills work correctly from the start. ## Core Features & Use Cases - Issue tracker setup: Detects the repo's remote and records whether issues live in GitHub, GitLab, local markdown under .scratch/, or another tracker, writing the choice to docs/agents/issue-tracker.md. - Triage label vocabulary: Records the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or custom overrides in docs/agents/triage-labels.md. - Domain doc layout: Configures single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts in docs/agents/domain.md. - Use Case: After installing the engineering skills into a GitHub repo, run this Skill once to generate the ## Agent skills block in CLAUDE.md and the supporting docs/agents/ files, so triage and ticketing skills immediately know how to operate. ## Quick Start Ask the agent to set up this repository for the engineering skills by configuring the issue tracker, triage labels, and domain docs.

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 skill once before using the other engineering skills. It explores your repo, asks about your issue tracker, triage labels, and domain doc layout, then writes configuration files under docs/agents/ and an Agent skills block 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 your git remote points at GitLab, the skill proposes GitLab and writes a docs/agents/issue-tracker.md based on the glab CLI template, covering issue creation, labels, notes, and merge request conventions.

What triage labels does the setup skill configure?▼

It configures five canonical roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. You can keep the defaults or provide custom label strings, which are recorded in docs/agents/triage-labels.md for the triage skill to use.

When should I use multi-context domain docs instead of single-context?▼

Use multi-context only when exploration finds monorepo signals like pnpm-workspace.yaml, a workspaces field in package.json, or populated packages directories. It creates a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files; most repos use the single-context default.

Do I need to re-run the setup skill after editing the config files?▼

No. You can edit the files under docs/agents/ directly at any time. Re-running the skill is only necessary if you want to switch issue trackers or restart the configuration from scratch.