Herdr Issue Triage
Use this skill only inside the herdr repository.
When the user says triage, inspect open GitHub issues for herdrdev/herdr and return a concise Markdown table. Prefer GitHub MCP tools when available. If they are unavailable, use gh issue list / gh issue view only when authenticated access is already configured.
Use this table shape:
| Light |
Recommendation |
Issue |
Age |
Reactions |
Why |
| 🔴 |
fix now |
#123 |
18d |
5 |
user-visible regression |
| 🟡 |
queue |
#124 |
42d |
2 |
useful but not blocking |
| 🔵 |
defer |
#125 |
7d |
0 |
cosmetic polish |
Keep issue numbers as Markdown links. Use days since issue creation for Age. Use total reactions for Reactions; include a compact breakdown only when it changes interpretation, such as 7 (5 👍, 2 👀).
Classify with these lights:
- 🔴
fix now: reproducible bug, crash, data loss, blocked workflow, release risk, or high-confidence user-visible regression.
- 🟡
queue: useful feature, important quality issue, repeated user signal, stale issue that still looks valid, or behavior worth scheduling.
- 🔵
defer: cosmetic polish, low-signal idea, unclear report, docs-only nit, or issue that likely needs more evidence before implementation.
Recommendations should be short imperative phrases: fix now, queue, defer, needs repro, close?, or needs owner decision.
Write one sentence before the table only if needed to state scope, such as how many open issues were inspected. After the table, add at most one short note for uncertainty or follow-up. Do not produce a long narrative unless the user asks for depth.
1---2name: triage-23description: Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.4---56# Herdr Issue Triage78Use this skill only inside the herdr repository.910When the user says `triage`, inspect open GitHub issues for `herdrdev/herdr` and return a concise Markdown table. Prefer GitHub MCP tools when available. If they are unavailable, use `gh issue list` / `gh issue view` only when authenticated access is already configured.1112Use this table shape:1314| Light | Recommendation | Issue | Age | Reactions | Why |15|---|---|---|---:|---:|---|16| 🔴 | fix now | [#123](https://github.com/herdrdev/herdr/issues/123) | 18d | 5 | user-visible regression |17| 🟡 | queue | [#124](https://github.com/herdrdev/herdr/issues/124) | 42d | 2 | useful but not blocking |18| 🔵 | defer | [#125](https://github.com/herdrdev/herdr/issues/125) | 7d | 0 | cosmetic polish |1920Keep issue numbers as Markdown links. Use days since issue creation for `Age`. Use total reactions for `Reactions`; include a compact breakdown only when it changes interpretation, such as `7 (5 👍, 2 👀)`.2122Classify with these lights:2324- 🔴 `fix now`: reproducible bug, crash, data loss, blocked workflow, release risk, or high-confidence user-visible regression.25- 🟡 `queue`: useful feature, important quality issue, repeated user signal, stale issue that still looks valid, or behavior worth scheduling.26- 🔵 `defer`: cosmetic polish, low-signal idea, unclear report, docs-only nit, or issue that likely needs more evidence before implementation.2728Recommendations should be short imperative phrases: `fix now`, `queue`, `defer`, `needs repro`, `close?`, or `needs owner decision`.2930Write one sentence before the table only if needed to state scope, such as how many open issues were inspected. After the table, add at most one short note for uncertainty or follow-up. Do not produce a long narrative unless the user asks for depth.
gabrielmoreira