---
name: Triage
slug: triage-4
category: Automation
description: Triage inspects open issues in the herdr repository and returns a concise decision-first Markdown table with priority lights and recommendations. Use it when asked to triage open issues or determine which issues need attention.
github: "https://github.com/herdrdev/herdr/tree/master/.agents/skills/triage"
language: Rust
stars: 28752
forks: 2045
install: "npx degit https://github.com/herdrdev/herdr/tree/master/.agents/skills/triage ~/.claude/skills/triage"
installs_to: ~/.claude/skills/triage
source_path: .agents/skills/triage/SKILL.md
collection_size: 5
category_size: 1523
collection_url: "https://dirskills.com/collections/herdrdev/herdr"
added: 2026-08-14T07:11:49.621Z
last_synced: 2026-08-14T07:11:49.621Z
canonical_url: "https://dirskills.com/skills/triage-4"
---

# Triage

Triage inspects open issues in the herdr repository and returns a concise decision-first Markdown table with priority lights and recommendations. Use it when asked to triage open issues or determine which issues need attention.

**Install:**

```bash
npx degit https://github.com/herdrdev/herdr/tree/master/.agents/skills/triage ~/.claude/skills/triage
```

## README

# 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](https://github.com/herdrdev/herdr/issues/123) | 18d | 5 | user-visible regression |
| 🟡 | queue | [#124](https://github.com/herdrdev/herdr/issues/124) | 42d | 2 | useful but not blocking |
| 🔵 | defer | [#125](https://github.com/herdrdev/herdr/issues/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.