triage-sweep

Classifies open issues and backlog items against live code to close completed work.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill triage-sweep-bravros
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: triage-sweep
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/triage-sweep
Command: npx skills add https://github.com/bravros/bravros --skill triage-sweep-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Stale issue trackers and backlogs accumulate items that are already implemented, duplicated, or no longer needed, and manually verifying each one against the current codebase is slow and error-prone. This Skill drains that queue by establishing the current truth for every item against live code, with an independent verifier gating every automatic close. ## Core Features & Use Cases - Read-only parallel triage: Dedups and classifies each issue and backlog item across four dimensions β€” code on the staging branch, active worktrees, open PRs, and .planning plan folders β€” without mutating anything. - Evidence-gated auto-close: An item closes only when classified already-done or solved-differently with a concrete artifact reference (commit SHA, merged PR, plan id, or file:line) confirmed by an independent adversarial verifier. - Serial apply with ledger events: Applies GitHub issue closes and append-only events to .planning/events.jsonl one at a time, then writes a sweep ledger summarizing every verdict. - Use Case: A repository has 60 open issues and 30 backlog items accumulated over months. Run the sweep to close the 20 already shipped, collapse duplicates, label the genuinely open work as fix-ready, and hand that set to a fix loop. ## Quick Start Ask the agent to run a triage sweep over all open GitHub issues and the .planning backlog to close items already implemented on the staging branch.

Frequently Asked Questions about triage-sweep

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

FAQPage Schema
How do I clean up a stale GitHub issue backlog automatically?β–Ό

Run a triage sweep that dedups the queue, classifies each item against the live code on your staging branch, and closes only items proven already-done with a concrete artifact reference. Everything else is labeled (fix-ready, deferred, skip) and left open for humans.

How does the sweep avoid closing issues that are not actually done?β–Ό

Every close-eligible verdict must cite a concrete artifact_ref such as a commit SHA, merged PR, plan id, or file:line, and an independent adversarial verifier must confirm it. Unverified or refuted closes are labeled fix-ready and left open.

Does the triage workflow modify code or issues while classifying?β–Ό

No. The classification fan-out is strictly read-only; it never closes issues, edits files, or appends ledger events. All mutations β€” gh issue close commands and .planning/events.jsonl appends β€” are applied serially afterward by the calling skill.

Can I inject project-specific rules into the triage classification?β–Ό

Yes. Pass free-text rules via args.guards, which are injected verbatim into every classifier prompt. For example, a rule can force any change touching a wire contract to be classified as human-only-integration.

What happens to items with an open PR or duplicate backlog ids?β–Ό

Items being actively built in an open PR or worktree are classified in-flight, labeled deferred, and never closed. Backlog items with duplicate-id twin files or frontmatter/filename desyncs are flagged as ledger defects and reported for human resolution, never auto-closed.