Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.
npx skills add https://github.com/1arley/volibear --skill triage-1arley
Please help me install this Agent Skill. Skill: triage Source: https://github.com/1arley/volibear/tree/main/.agents/skills/triage Command: npx skills add https://github.com/1arley/volibear --skill triage-1arley
.out-of-scope/ files and surface prior rejections when similar requests reappear. - Use Case: A maintainer says "Let's look at #42". The Skill reads the issue, checks the codebase for existing implementations and prior rejections, verifies the claim, grills the reporter if details are missing, then posts an agent brief and moves the issue to ready-for-agent. ## Quick Start Ask the assistant to triage issue #42 on the repository's issue tracker and move it to the appropriate state.High-intent search queries and answers about installing and using this skill.
Invoke the triage workflow with a natural language request like "show me anything that needs my attention" or "let's look at #42". The Skill reads the issue, checks the codebase for existing implementations, verifies claims, and recommends a category and state before applying labels and comments.
An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative specification for an autonomous coding agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.
Yes, external PRs are treated as issues with attached code, using the same roles and states. The Skill checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing what remains to finish or fix the existing diff.
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 issues are matched against these files by concept similarity, and prior rejections are surfaced to the maintainer before re-litigating.
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 the work cannot be delegated.
U1traVenoMove GitHub issues and external PRs through a triage state machine with agent-ready briefs.
SevWrenMove GitHub issues and external PRs through a triage state machine with agent-ready briefs.
akillnessValidate architecture plans against project domain language in CONTEXT.md and ADRs.
yamcodesCreates GitHub issues via gh CLI after interactive requirement clarification and triage labeling.