issue-grooming SKILL.md skillA
issue-grooming from sfc-gh-eraigosa/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sfc-gh-eraigosa/dotfiles/issue-grooming@git:20261019.0b11bcePins git:20261019.0b11bce in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sfc-gh-eraigosa/dotfiles
- Path
ai/skills/issue-grooming/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261019.0b11bce, committed Oct 19, 2026
- Size
- 8,134 bytes
- Repository stars
- 53
- License
- Apache-2.0
Use when the user wants to groom, triage, prioritize, or clean up the GitHub issue backlog of a repo: "groom the issues", "triage the backlog", "which issues are already done", "prioritize the open issues", "close stale issues", "label issues 1-5", "refactor old issues to match the repo", or a periodic backlog review — even when they do not say "grooming". Also use when a single old issue looks stale and the user asks whether it is still valid. Not for reviewing or merging PRs (pr-list / gss)…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# issue-grooming — groom the backlog against what actually shipped Grooming answers three questions for every open issue, with evidence from the repo rather than from the issue's own text: **is it already addressed**, **how important is it now**, and **does its body still describe work that fits the repo**. The output is a labelled, trimmed backlog and a report the owner can scan in a minute. Why the rigor: issues are written at a moment in time. In this repo code moves (`src/` → `sdk/`), leaves of a plan merge under PR titles that never mention the issue, follow-ups get absorbed by later objectives, and a bot keeps filing reports. An issue's text is the *claim*; `main`, merged PRs, and `docs/mbo/index.md` are the *evidence*. Only the evidence decides. ## 0 — Setup (one command) ```bash bash ai/skills/issue-grooming/scripts/groom-snapshot.sh -o <scratch>/groom bash ai/skills/issue-grooming/scripts/groom-labels.sh # ensures priority:1..5 exist (idempotent) ``` The snapshot writes `issues.json`/`issues.txt` (bodies + comments), `labels.json`, `merged-prs.json` (with the issues each PR closed), and `clusters.txt` (a first-cut grouping). …
Read the whole file at its exact version.
How to install
mdr add sfc-gh-eraigosa/dotfiles/issue-grooming@sha256:bd0202e318b1b985The line at the top of this page pins the label git:20261019.0b11bce, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2bgigblrldjm5j3b)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8134 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sfc-gh-eraigosa/dotfiles · 53 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2bgigblrldjm5j3b GET https://markdownregistry.com/api/v1/resolve?ref=sfc-gh-eraigosa/dotfiles/issue-grooming GET https://markdownregistry.com/api/v1/blob/bd0202e318b1b98566c3352b278c022a8a264183deb84443407a6e496e351ade
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.