setup-matt-pocock-skills

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill setup-matt-pocock-skills-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/setup-matt-pocock-skills
Command: npx skills add https://github.com/marjorg/setup --skill setup-matt-pocock-skills-marjorg

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 from consistent, well-defined files instead of guessing. ## 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 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 label strings actually used in the repo's tracker. - Domain doc layout: Records whether the repo uses a single-context layout (CONTEXT.md + docs/adr/) or a multi-context layout with CONTEXT-MAP.md for monorepos. - Use Case: After installing the engineering skills into a GitHub repo, run this Skill once to generate docs/agents/ config files and an ## Agent skills block in CLAUDE.md, so subsequent triage and ticket workflows operate against GitHub Issues with the correct labels. ## Quick Start Ask the agent to run the setup-matt-pocock-skills skill 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 Matt Pocock's 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 and triage labels, then writes config files under docs/agents/ and an Agent skills block in CLAUDE.md or AGENTS.md.

How do I set up issue tracking for AI agent workflows?

The skill supports GitHub Issues via the gh CLI, GitLab Issues via the glab CLI, and local markdown files under .scratch/. It records your choice in docs/agents/issue-tracker.md so skills like triage and to-tickets know where to read and write issues.

Does this skill work with GitLab instead of GitHub?

Yes, GitLab is supported out of the box using the glab CLI, with a dedicated seed template covering issue creation, notes, labels, and merge request handling. The skill detects GitLab from your git remote and proposes it automatically.

What triage labels does the skill configure?

It configures five canonical labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. You can keep the defaults or map them to your tracker's existing label strings, recorded in docs/agents/triage-labels.md.

When should I use multi-context domain docs layout?

Use multi-context layout only when the repo is a genuine monorepo, signaled by pnpm-workspace.yaml, a workspaces field, or populated packages directories. It creates a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files; single-context fits almost every repo.

Do I need to re-run the setup skill after editing 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.