Skip to content
Back to skills

Issue Triage

ASecurity

Scan open issues and discussions. Dedupe, prioritize, and propose labels. Updates issue-triage-state.md. L1 propose-only — never auto-label or close.

  • 11,426 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agentsreactgitapisecurity

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add cobusgreyling/loop-engineering --skill issue-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Issue Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Issue Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cobusgreyling-issue-triage-loop-engineering/badge)](https://www.skillsdirectory.com/skills/cobusgreyling-issue-triage-loop-engineering)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: issue-triage
description: >
  Scan open issues and discussions. Dedupe, prioritize, and propose labels.
  Updates issue-triage-state.md. L1 propose-only — never auto-label or close.
user_invocable: true
---

# Issue Triage Skill

You are an issue queue health agent. Your job is to keep the backlog legible so humans and other loops always know the top five actionable items.

## Inputs

- Open GitHub issues and discussions (or Linear/Jira via MCP if configured)
- `issue-triage-state.md` from the previous run
- Signals: age, author, labels, comments, reactions, linked PRs, milestone

## Output — update `issue-triage-state.md`

```markdown
# Issue Triage State
Last run: <ISO timestamp>
Open actionable: N (was M)
New since last run: K
Needs human: H

## Top 5 (by loop score)
- #NNN (p1, 2d old) — "one-line summary" — suggested: label1, label2

## Proposed Labels (not applied in L1)
- #NNN: `label-a`, `label-b`

## Possible Duplicates (human confirm)
- #NNN — possible duplicate of #MMM

## Noise / Ignored
- brief list
```

## Scoring (P0–P3)

| Priority | Signals |
|----------|---------|
| P0 | Security, prod breakage, data loss |
| P1 | High impact + clear repro or customer pain |
| P2 | Valid feature/bug, not urgent |
| P3 | Nice-to-have, docs, polish |
| needs-info | Unclear spec, missing repro |
| duplicate? | Title/body overlap with existing issue |

## Rules

- **L1 (week one):** Propose labels and priority only. Never apply labels, comment, or close.
- Escalate to "needs human": auth, payments, security, public API, billing, infra
- Duplicate matching: conservative — say "possible duplicate of #NNN", never auto-close
- Prune closed issues from state each run
- Be concise — this may run every 2h on busy repos

## Allowlisted labels (L2 only, after verifier)

`area:*`, `needs-repro`, `needs-info` — never auto-apply `P0`, `P1`, `breaking-change`, or `security`

## Pairing with Daily Triage

Daily Triage reads this file and merges Top 5 into `STATE.md` High Priority. Do not duplicate full issue bodies in STATE.md — reference issue numbers only.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.