triage

Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill triage-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/triage
Command: npx skills add https://github.com/falentio/cimi --skill triage-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs that lack clear categorization, verification, and actionable specifications. This Skill structures the entire triage workflow so every issue ends up with a clear category, state, and either an agent-ready brief or a documented rejection. ## Core Features & Use Cases - State machine triage: Move issues and PRs through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with category labels (bug, enhancement). - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds to flesh out vague requests. - Agent brief generation: Write durable, behavioral agent briefs with acceptance criteria and scope boundaries for AFK agents to execute. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and deduplicate new requests against prior rejections. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, converts a feature request into an agent brief, and closes a duplicate dark-mode request by referencing the existing out-of-scope record. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue or PR number to triage it directly.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues with an AI assistant?

Invoke the triage workflow in natural language, such as asking what needs attention or naming a specific issue number. The assistant gathers context, verifies claims against the codebase, recommends a category and state, and applies labels with comments.

What is an agent brief for GitHub issues?

An agent brief is a structured comment posted when an issue reaches ready-for-agent state. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous agent can implement it.

Can triage handle external pull requests as well as issues?

Yes, external PRs are treated as issues with attached code and move through the same states. The assistant checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing remaining work.

How does the out-of-scope knowledge base prevent duplicate feature requests?

Rejected enhancement requests are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and prior issue links. During triage, new requests are matched against these files by concept similarity and surfaced to the maintainer.

When should an issue go to ready-for-human instead of ready-for-agent?

Use ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief uses the same structure but notes why delegation is not possible.