issue-triage SKILL.md skillB
issue-triage from philoserf/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add philoserf/claude-code-config/issue-triage@git:20261025.c16263aPins git:20261025.c16263a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- philoserf/claude-code-config
- Path
skills/issue-triage/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261025.c16263a, committed Oct 25, 2026
- First version recorded
- Sep 25, 2026
- Size
- 7,235 bytes
- Repository stars
- 13
- License
- MIT
Organizes filed issues into milestones and repairs their metadata — severity labels and blocked-by relations. Use when sorting a backlog, planning a release's scope, recording what blocks what, or when issues have been filed but not placed.
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 triage The step between filing issues and working them. A finding written to `.issues/` and pushed to GitHub arrives with a title, a body and a label; it does not arrive knowing which release it belongs to, what it waits on, or how severe it really is. This skill supplies that. Triage is about **placement**, not truth. Whether a finding is still correct is `issue-verify`'s question, and a freshly filed issue usually has not had time to go stale. ## Start with the audit ```bash ~/.claude/skills/issue-triage/scripts/issue-meta.sh audit [milestone] ``` One row per open issue, then a `GAP` line for every missing piece. Exit `2` means gaps were found. With no argument it audits the whole open backlog, which is the right way to catch an issue that was filed and then forgotten because it belonged to no milestone. ## Deciding the milestone The question is not "is this important" but **"what breaks if this ships in the same release as everything else in that milestone"**. - **A behaviour change belongs in a minor**, not a patch — including a bug fix that moves values callers may have pinned. …
Read the whole file at its exact version.
How to install
mdr add philoserf/claude-code-config/issue-triage@sha256:cf99cfaa72cc935eThe line at the top of this page pins the label git:20261025.c16263a, 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_onzm6dlw74sjr347)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 25, 2026 and Oct 25, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.c16263a latest | 2026-10-25 | c16263a | 7,235 B | B | view · diff |
| git:20261011.24502df | 2026-10-11 | 24502df | 7,243 B | B | view · diff |
| git:20261011.40a912a | 2026-10-11 | 40a912a | 4,798 B | B | view · diff |
| git:20260925.2a8135d | 2026-09-25 | 2a8135d | 5,371 B | B | view · diff |
| git:20260925.cbdd1ce | 2026-09-25 | cbdd1ce | 5,143 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7235 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
philoserf/claude-code-config · 13 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_onzm6dlw74sjr347 GET https://markdownregistry.com/api/v1/resolve?ref=philoserf/claude-code-config/issue-triage GET https://markdownregistry.com/api/v1/blob/cf99cfaa72cc935ee509b9713797605dac187ea98fd040bc36a718f940e6f913
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.
More from philoserf/claude-code-config
Every file in philoserf/claude-code-config