AugmentClaude

GitHub Issue Triage

Organize open GitHub issues into a prioritized table with recommendations.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/triage-ogulcancelik/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

Herdr Issue Triage

Use this skill only inside the herdr repository.

When the user says triage, inspect open GitHub issues for ogulcancelik/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:

LightRecommendationIssueAgeReactionsWhy
🔴fix now#12318d5user-visible regression
🟡queue#12442d2useful but not blocking
🔵defer#1257d0cosmetic 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.

Related skills