setup-matt-pocock-skills

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill setup-matt-pocock-skills-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill setup-matt-pocock-skills-tanqimin

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 tracker, 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 repo's actual label strings in docs/agents/triage-labels.md. - Domain doc layout: Records single-context or multi-context layout for CONTEXT.md and ADR files, plus consumer rules, in docs/agents/domain.md, and adds an Agent skills block to CLAUDE.md or AGENTS.md. - Use Case: After installing a set of engineering skills in a GitHub repo, run this once to generate the docs/agents configuration files so triage and ticket-creation skills operate against GitHub Issues with the correct labels. ## Quick Start Ask the agent to run the setup 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 configure a repo for engineering skills like triage and to-tickets?

Run this setup skill once per repository. It explores your git remote and existing docs, asks which issue tracker you use, then writes configuration files under docs/agents/ and an Agent skills block in CLAUDE.md or AGENTS.md.

Which issue trackers does this 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.

What are the default triage labels?

The five canonical labels are needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. If your tracker already uses different names, you can provide overrides so the triage skill applies your existing labels instead of creating duplicates.

Does this skill work with monorepos?

Yes. It detects monorepo signals such as pnpm-workspace.yaml or a workspaces field in package.json, then offers a multi-context domain doc layout with a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files.

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 routine changes, you can edit the generated files under docs/agents/ directly.