setup-matt-pocock-skills

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill setup-matt-pocock-skills-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/setup-matt-pocock-skills
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill setup-matt-pocock-skills-fatih0234

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 skill reads consistent settings instead of guessing. ## Core Features & Use Cases - Issue tracker setup: Detects GitHub or GitLab remotes and records the tracker choice (GitHub, GitLab, local markdown under .scratch/, or a custom workflow) in docs/agents/issue-tracker.md. - Triage label vocabulary: Writes the five canonical triage labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or your custom overrides to 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, and adds an Agent skills block to CLAUDE.md or AGENTS.md. - Use Case: After installing the engineering skills into a GitHub repo, run this once to record that issues live in GitHub Issues, keep the default triage labels, and use a single-context domain layout. ## Quick Start Run the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain documentation layout 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 set up issue tracking for AI engineering skills in my repo?▼

Run this setup skill once in your repository. It inspects your git remote to detect GitHub or GitLab, asks which tracker you use, and writes the choice to docs/agents/issue-tracker.md so other skills know whether to call gh, glab, or write local markdown files.

What triage labels does the setup configure?▼

It configures five canonical labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. You can keep these defaults or provide overrides matching your tracker's existing vocabulary, recorded in docs/agents/triage-labels.md.

Does this skill work with GitLab or only GitHub?▼

It supports GitHub, GitLab, local markdown files under .scratch/, and custom trackers like Jira or Linear. GitHub uses the gh CLI and GitLab uses the glab CLI, with seed templates provided for each.

Can I use this with a monorepo or multi-context codebase?▼

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

When should I re-run the repository setup skill?▼

Re-run it only when switching issue trackers or restarting configuration from scratch. For ordinary changes, edit the files under docs/agents/ directly, since the skill is designed as a one-time bootstrap.