skills.rest
CYRUS-pinto
CYRUS-pintoCOMMUNITY
Explore all skills by this author →
GitHub

setup-matt-pocock-skills

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

Updated Sep 11, 2026
Search Tags:#github#issue tracker#configuration#gitlab#repository setup#triage labels#domain docs
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill setup-matt-pocock-skills-cyrus-pinto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill setup-matt-pocock-skills-cyrus-pinto

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 workflow, 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 when the triage skill is installed. - Domain doc layout: Configures single-context (CONTEXT.md plus docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts based on monorepo signals. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it inspects git remotes and existing CLAUDE.md/AGENTS.md files, confirms choices with you, then writes an Agent skills block and the docs/agents/ configuration files. ## Quick Start Ask the AI to run the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain docs before using the other 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 the Matt Pocock engineering skills?▼

Run the setup-matt-pocock-skills skill once before using the other engineering skills. It explores your repo, confirms choices with you section by section, 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 solo projects. 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, GitLab is supported through the glab CLI with a dedicated seed template covering issue creation, notes, labels, and merge request handling. The skill proposes GitLab automatically when your git remote points at gitlab.com or a self-hosted GitLab host.

What triage labels does the skill configure?▼

It records five canonical roles: 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, and the mapping is written to docs/agents/triage-labels.md.

When should I choose multi-context domain docs over single-context?▼

Choose multi-context only when exploration finds monorepo signals like pnpm-workspace.yaml, a workspaces field in package.json, or populated packages directories. Single-context with one CONTEXT.md and docs/adr/ at the root fits almost every repo and is the 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.

Related Skills

Explore More Software Engineering Skills→
taptaptaptap

git-remote-operations

Manage Git remote PRs, issues, and CI/CD pipelines via gh or glab CLIs.

Official
Intermediate
shushuznshushuzn
4

setup-matt-pocock-skills

Configure engineering-skills context with issue tracker and triage label settings.

Community
Intermediate
stacksjsstacksjs
625

stacks-domain-modeling

Builds and sharpens a Stacks project's domain language through CONTEXT.md glossaries and ADRs.

Official
Intermediate
matlabmatlab
883

matlab-model-via

Model signal and ground return vias for multi-layer PCB transitions in MATLAB.

Official
Advanced