skills.rest
PVMalove
PVMaloveCOMMUNITY
Explore all skills by this author →
GitHub

triage

Move issues and external PRs through a label-based triage state machine.

Updated Aug 19, 2026
Search Tags:#issue tracker#pull requests#github issues#triage#label taxonomy#agent brief#workflow state machine
One-click install
npx skills add https://github.com/PVMalove/claude-agent-harness --skill triage-pvmalove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/PVMalove/claude-agent-harness/tree/main/skills/first-party/pvmalove/triage
Command: npx skills add https://github.com/PVMalove/claude-agent-harness --skill triage-pvmalove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in untriaged issues and external PRs with no consistent process for categorizing, verifying, and routing work. This Skill enforces a structured triage workflow that classifies every item, verifies claims against the codebase, and produces agent-ready briefs so nothing sits ambiguous. ## Core Features & Use Cases - Label-based state machine: Applies a namespaced taxonomy (bug/enhancement, workflow::specs/ready/in-progress/blocked, hitl/afk) so every issue carries exactly one label per required axis. - Verification and grilling: Reproduces reported bugs, checks out PR diffs to confirm claims, and invokes grilling and domain-modeling skills to flesh out underspecified requests. - Agent briefs and out-of-scope knowledge base: Writes durable, behavioral agent briefs for afk-ready work and records rejected feature requests in .out-of-scope/ files to deduplicate future requests. - Use Case: A maintainer runs /triage on Monday morning, sees three buckets (unlabeled, partially triaged, blocked with reporter activity), picks issue #42, verifies the reported bug, and posts an agent brief so an AFK agent can implement the fix. ## Quick Start Ask the agent to triage issue #42 by reading it fully, verifying the claim against the codebase, and recommending category, execution mode, and workflow state labels.

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 agent?▼

Invoke /triage and describe what you want in natural language, such as "show me anything that needs my attention" or "let's look at #42". The skill reads the full issue, verifies claims against the codebase, and recommends category, execution mode, and workflow state labels before applying them.

What labels does the triage workflow use?▼

Every triaged issue carries exactly one category label (bug or enhancement), one workflow state label (workflow::specs, ready, in-progress, or blocked), and once it leaves specs, one execution mode label (hitl or afk). The out-of-scope label replaces wontfix for rejected requests.

Can triage handle external pull requests as well as issues?▼

Yes, when the issue-tracker config treats external PRs as a request surface, a PR is triaged as an issue with attached code using the same roles and states. The skill checks out the diff and runs relevant tests to verify the PR does what it claims.

What is an agent brief and when is it written?▼

An agent brief is a structured comment posted when an issue reaches workflow::ready with afk mode, serving as the authoritative specification for an autonomous agent. It describes desired behavior, key interfaces, acceptance criteria, and scope boundaries without referencing file paths or line numbers.

How does the .out-of-scope directory prevent duplicate feature requests?▼

Rejected feature requests are recorded as concept files in .out-of-scope/ with the decision, reasoning, and prior request links. During triage, new issues are matched against these files by concept similarity, and matches are surfaced to the maintainer before re-litigating.

When should an issue go to workflow::blocked instead of ready?▼

Route to workflow::blocked when the issue depends on another ticket or lacks information from the reporter, posting triage notes that capture what is established and specific questions still needed. It returns to ready once the blocker clears, handled by /implement when work starts.

Related Skills

Explore More Software Engineering Skills→
The-Vibe-CompanyThe-Vibe-Company
2.4k

triage

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

Official
Advanced
akillnessakillness
40

to-issues

Convert plans, specs, or requirements into vertical slice issues.

Community
Intermediate
matt-rileymatt-riley
1

grill-me

Interrogate plans or designs through structured one-question-at-a-time questioning.

Community
Advanced
Nellur35Nellur35

mapping

Label and validate codebase components by trustworthiness with human questionnaires.

Community
Advanced