pocock-setup

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

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-setup-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocock-setup
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/mattpocock/pocock-setup
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-setup-l0lxl0lw

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 use, 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: 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 + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts in docs/agents/domain.md, and adds an Agent skills section to CLAUDE.md or AGENTS.md. - Use Case: After cloning the engineering skills into a GitHub repo, run this once to generate the docs/agents/ configuration files so triage and ticket-creation skills immediately know to use gh issue commands with the default labels. ## Quick Start Ask the AI to run the pocock-setup skill to configure this repository's issue tracker, triage labels, and domain documentation layout.

Frequently Asked Questions about pocock-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up issue tracking configuration for AI engineering skills?

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

What triage labels does the setup 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 custom label strings that map to your tracker's existing vocabulary.

Does this skill work with GitLab or only GitHub?

It supports GitHub via the gh CLI, GitLab via the glab CLI, and local markdown files under .scratch/. It detects the remote host during exploration and proposes the matching tracker, and also accepts custom workflows described in prose.

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

Multi-context layout with a root CONTEXT-MAP.md is only offered when exploration finds monorepo signals like pnpm-workspace.yaml or a workspaces field. Almost every repo uses the default single-context layout with one CONTEXT.md and docs/adr/.

Do I need to rerun the setup after editing the generated files?

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