skilld
All skills
mattpocock avatar

/setup-matt-pocock-skills

@5c89081 official
by Matt Pocockmattpocock/skills274k stars
22,991

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Ask your Agent

Use this Skill: https://skilld.dev/gh/mattpocock/skills/setup-matt-pocock-skills

This session only. Nothing lands on disk.

issue-tracker-local.md

≈453 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Issue tracker: Local Markdown

Issues and specs for this repo live as markdown files in .scratch/.

Conventions

  • One feature per directory: .scratch/<feature-slug>/
  • The spec is .scratch/<feature-slug>/spec.md
  • Implementation issues are one file per ticket at .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from 01, never a single combined tickets file
  • Triage state is recorded as a Status: line near the top of each issue file (see triage-labels.md for the role strings)
  • Comments and conversation history append to the bottom of the file under a ## Comments heading

When a skill says "publish to the issue tracker"

Create a new file under .scratch/<feature-slug>/ (creating the directory if needed).

When a skill says "fetch the relevant ticket"

Read the file at the referenced path. The user will normally pass the path or the issue number directly.

Wayfinding operations

Used by /wayfinder. The map is a file with one child file per ticket.

  • Map: .scratch/<effort>/map.md (the Notes / Decisions-so-far / Fog body).
  • Child ticket: .scratch/<effort>/issues/NN-<slug>.md, numbered from 01, with the question in the body. A Type: line records the ticket type (research/prototype/grilling/task); a Status: line records claimed/resolved.
  • Blocking: a Blocked by: NN, NN line near the top. A ticket is unblocked when every file it lists is resolved.
  • Frontier: scan .scratch/<effort>/issues/ for files that are open, unblocked, and unclaimed; first by number wins.
  • Claim: set Status: claimed and save before any work.
  • Resolve: append the answer under an ## Answer heading, set Status: resolved, then append a context pointer (gist + link) to the map's Decisions-so-far in map.md.

Source: SKILL.md on GitHub

Third-party checks

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill scaffolds repository configuration by exploring files and using GitHub or GitLab CLI tools. The main security considerations are the ingestion of untrusted repository data which could influence agent actions, and access to local git configuration files.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Provenance

Signed by skilld at 5c89081. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 2 months ago

Capability

disable-model-invocation
true

Topics

  • Documentation
  • github
  • gitlab
  • configuration
  • agents
  • workflow
  • issue-tracker
  • triage

README badge

README badge for mattpocock/skills/setup-matt-pocock-skills

What it does

Sets up per-repo configuration files that the Matt Pocock engineering skills (triage, to-issues, diagnose, tdd, etc.) read to understand your issue tracker location, label vocabulary, and domain documentation layout. Run this once before using those skills, or if they appear to lack context about your repo's workflow and documentation structure.

Generated from the current SKILL.md.

Frequently asked

What does this skill do?
This skill scaffolds per-repo configuration files that other Matt Pocock engineering skills (to-issues, triage, diagnose, tdd, etc.) depend on: issue tracker location, triage label vocabulary, and domain docs layout.
When should I run this skill?
Run it once before first use of any dependent skill, or if those skills appear to be missing context about your issue tracker, triage labels, or domain docs. Re-run only if you want to switch issue trackers or restart configuration.
What issue trackers does this support?
GitHub (default), GitLab, local markdown under `.scratch/`, or any other tracker if you describe your workflow in prose.
Do I need to have existing labels in my issue tracker?
No. If your repo has no labels yet, the skill uses sensible defaults (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). If you already use different label names, you can map them so the skill applies the ones you've configured.
Does this work with monorepos?
Yes. The skill supports both single-context repos (one CONTEXT.md at the root) and multi-context layouts (CONTEXT-MAP.md pointing to per-context CONTEXT.md files).

Generated from the current SKILL.md. These answers refresh after source changes.