triage

# 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`, `...