Review open GitHub issues for herdr and organize them into a concise Markdown table. Each row shows urgency, a recommended action, issue age, reactions, and a short reason to help decide what needs attention.
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.
Review the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Control terminals and coding agents inside Herdr, a tool that groups multiple terminals. Create split panes, run commands, send agent prompts, read output, and wait for status changes while coordinating work across the current session.
Check release readiness inside the herdr repository by comparing changes since the base release with upcoming release notes and documentation. Review CLI descriptions, issue references, checks, and benchmarks, then report readiness.
Create a disposable Herdr session to reproduce terminal, process, API, or agent issues separately from the main session. Drive tests through the CLI or API, collect evidence of state changes, and clean up the temporary session afterward.