agentleFS
Sign inStart free
oneafrikanoneafrikan/the-grid/skills/setup-repo-skills/SKILL.md

setup-repo-skills

Skill4 starsChanged 10 days agoMITView on GitHub

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look at the current repo to understand its starting state.

    line 21
  2. Very specific:

    Read sections/explore-checklist.md for what to look at.

    line 23
  3. Very specific:

    Read sections/file-selection.md to pick which file to edit.

    line 54
  4. Very specific:

    Read sections/agent-skills-block.md for the block to write.

    line 56
  5. Distinctive:

    Read a section only when its condition applies.

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Matt Pocock's Skills

Scaffold the per-repo configuration that the engineering skills assume:

  • Issue tracker — where issues live (GitHub by default; local markdown is also supported out of the box)
  • Triage labels — the strings used for the five canonical triage roles
  • Domain docs — where CONTEXT.md and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

Process

1. Explore

Look at the current repo to understand its starting state. Read whatever exists; don't assume:

Read sections/explore-checklist.md for what to look at.

2. Present findings and ask

Summarise what's present and what's missing. Then walk the user through the three decisions one at a time — present a section, get the user's answer, then move to the next. Don't dump all three at once.

Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.

Section A — Issue tracker.

Read sections/issue-tracker.md.

Section B — Triage label vocabulary.

Read sections/triage-labels.md.

Section C — Domain docs.

Read sections/domain-docs.md.

3. Confirm and edit

Show the user a draft of:

  • The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)
  • The contents of docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md

Let them edit before writing.

4. Write

Read sections/file-selection.md to pick which file to edit.

Read sections/agent-skills-block.md for the block to write.

Then write the three docs files using the seed templates in this skill folder as a starting point:

  • issue-tracker-github.md — GitHub issue tracker
  • issue-tracker-gitlab.md — GitLab issue tracker
  • issue-tracker-local.md — local-markdown issue tracker
  • triage-labels.md — label mapping
  • domain.md — domain doc consumer rules + layout

For "other" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.

5. Done

Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit docs/agents/*.md directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.

Sections

Read a section only when its condition applies; do not preload them.

  • sections/explore-checklist.md: read when exploring the repo (step 1)
  • sections/issue-tracker.md: read when presenting Section A (issue tracker)
  • sections/triage-labels.md: read when presenting Section B (triage labels)
  • sections/domain-docs.md: read when presenting Section C (domain docs)
  • sections/file-selection.md: read when choosing which file to write the block into (step 4)
  • sections/agent-skills-block.md: read when writing the ## Agent skills block (step 4)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free