pr-grooming SKILL.md skillA
pr-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/pr-grooming@git:20261018.14e6c57Pins git:20261018.14e6c57 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/pr-grooming/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261018.14e6c57, committed Oct 18, 2026
- Size
- 10,785 bytes
- Repository stars
- 53
- License
- Apache-2.0
Use when the user wants to groom, triage, or clean up the open pull requests of a repo: "groom the PRs", "review the open PRs", "which drafts are stale", "close old draft PRs", "rebase the dependabot PRs", "are the open PRs still mergeable", "refresh that old bugfix PR", or a periodic PR review — even when they do not say "grooming". Also use when a single old PR looks abandoned and the user asks whether it still applies. Not for listing PRs in chat (pr-list), not for the issue backlog…
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
# pr-grooming — decide the fate of every open PR against `main` A PR grooming pass answers, for every open PR, **does this still apply**, **what does it need to land** (a rebase, a refresh, a decision), and **who acts next**. The output is a shorter PR list where each survivor is rebased, CI-verified and either queued or clearly waiting on a human, plus a report the owner can scan in a minute. Why the rigor: in this repo drafts are cheap (`gss feature worker add` opens one per leaf), so they pile up — design docs written for a CLI that was retired, plans that later merged under a different objective, WIP parked "to decide later". A PR's own description says what it *was*; `main`, `docs/mbo/index.md` and the merged-PR list say what is *still true*. Only the evidence decides, and every close names its successor so nothing is lost (branches are never deleted). ## 0 — Setup (one command) ```bash bash ai/skills/pr-grooming/scripts/pr-snapshot.sh -o <scratch>/pr-groom ``` `triage.tsv` gives each PR a first-cut **category**, age, draft state, merge state and CI state; `prs.txt` has bodies, files, comments and check names; `mbo-rows.txt` lists the …
Read the whole file at its exact version.
How to install
mdr add sfc-gh-eraigosa/dotfiles/pr-grooming@sha256:d2f0acf8b9cd5a06The line at the top of this page pins the label git:20261018.14e6c57, 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_tfyiircqv4gdrt7s)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 18, 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 (10785 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-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tfyiircqv4gdrt7s GET https://markdownregistry.com/api/v1/resolve?ref=sfc-gh-eraigosa/dotfiles/pr-grooming GET https://markdownregistry.com/api/v1/blob/d2f0acf8b9cd5a0644db298785df3bc76b6f5b604adb6a55ea87a57f304e8812
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.