setup-matt-pocock-skills

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/julianckt/adoptarun --skill setup-matt-pocock-skills-julianckt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/julianckt/adoptarun/tree/main/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/julianckt/adoptarun --skill setup-matt-pocock-skills-julianckt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where issues live, which label vocabulary to apply, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other skill reads consistent conventions 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 repo's actual label strings, only when the triage skill is installed. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) structure for monorepos. - Use Case: After cloning a repo and installing the engineering skills, run this once to generate docs/agents/*.md files and an Agent skills section in CLAUDE.md or AGENTS.md that all other skills consume. ## Quick Start Ask the agent to run the setup 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 set up issue tracking conventions for AI engineering skills?

Run this setup skill once in the repo. It explores your git remote and existing files, asks which tracker you use (GitHub, GitLab, local markdown, or other), then writes docs/agents/issue-tracker.md that other skills read for all issue operations.

What triage labels does the setup skill configure?

It configures five canonical triage roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. The defaults are written as-is, but you can override the label strings to match your tracker's existing vocabulary. This section is skipped if the triage skill is not installed.

Does the setup skill support GitLab or only GitHub?

It supports GitHub, GitLab, and local markdown issue trackers out of the box, with seed templates for each. GitHub uses the gh CLI, GitLab uses the glab CLI, and local markdown stores issues as files under .scratch/. Other trackers like Jira can be recorded as freeform prose.

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

Multi-context layout with a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files is only offered when the skill detects monorepo signals like pnpm-workspace.yaml or a workspaces field. Single-context with one CONTEXT.md and docs/adr/ fits almost every repo.

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

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