triage

Classify issues and PRs through a state machine and produce agent-ready briefs.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill triage-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/engineering/skills/triage
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill triage-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Incoming issues and PRs often arrive vague, mislabeled, or missing reproduction details, causing wasted agent runs and endless back-and-forth with reporters. This Skill classifies each item, moves it through explicit states, and only produces an execution brief when the work is genuinely ready. ## Core Features & Use Cases - State machine routing: Move items through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix with clear exit criteria. - Verification before questioning: Search code, logs, git history, and existing issues before asking the reporter anything, so only truly blocking questions get asked. - Structured agent briefs: Output a complete brief with problem statement, reproduction steps, scope, acceptance criteria, and a verification plan that downstream skills like debug, to-spec, and implement can consume directly. - Use Case: A vague bug report lands saying "checkout is broken." The Skill reproduces the error from linked logs, checks recent commits to the payment module, assigns severity S2, and emits a ready-for-agent brief routed to debug and implement — without asking the reporter a single unnecessary question. ## Quick Start Triage this issue report, verify what you can from the codebase and logs, then classify it and output either an agent brief or the blocking questions.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage bug reports before assigning them to a developer?▼

Classify the report by category and severity, verify what you can from logs, git history, and the codebase, then move it through states like needs-info or ready-for-agent. Only assign it once reproduction steps, scope, and acceptance criteria are complete.

What should an agent-ready issue brief contain?▼

A complete brief includes the problem statement, reproduction steps with expected versus actual behavior, in-scope and out-of-scope boundaries, likely files involved, acceptance criteria, known constraints, and a verification plan proving the fix works.

How do I avoid asking reporters unnecessary questions during triage?▼

Attempt verification first: reproduce the issue, run git log on affected files, search for duplicate reports, and check feature flags and deployment versions. Only ask questions whose answers change routing or priority and cannot be discovered independently.

When should an issue be marked wontfix instead of triaged?▼

Mark wontfix when the item is a duplicate, invalid, or explicitly out of scope. Always link the duplicate or record a one-line reason so future readers understand the decision without re-investigating.

How should large pull requests without descriptions be handled?▼

Route PRs with diffs over 400 lines and no description to needs-info and request a summary and test plan. PRs touching auth, payments, or migrations should additionally get code review and deployment checklist requirements added to the brief.