triage

Triage CI failures, issues, commits, and PRs into actionable findings.

1.6k|122|Updated Sep 21, 2025
One-click install
npx skills add https://github.com/bitbonsai/mcpvault --skill triage-bitbonsai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/bitbonsai/mcpvault/tree/main/skills/triage
Command: npx skills add https://github.com/bitbonsai/mcpvault --skill triage-bitbonsai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage keeps a repository from getting stuck by turning CI failures, open issues, recent commits, and contributor PRs into clear next actions instead of silent limbo.

Core Features & Use Cases

  • Signal collection: Reads failures, issues, commits, and open threads to identify what changed and what still needs attention.
  • Safe fix fan-out: Drafts small, test-backed fixes in isolated worktrees when a problem is mechanical and bounded.
  • Review-first workflow: Checks whether an existing contributor PR already addresses the problem and reviews it instead of competing with it.
  • Stateful follow-up: Persists run history, dedupes repeated findings, and keeps open commitments visible so the next run resumes cleanly.

Quick Start

Activate the triage skill to inspect recent repository signals, review existing contributor PRs, and prepare the smallest safe response for each finding.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage CI failures and open issues in a GitHub repository?

Triage CI failures and open issues by collecting repository signals, deduping repeated findings, and preparing bounded fixes or review recommendations. This requires GitHub CLI access and git worktrees to safely isolate drafted changes.

Can I draft test-backed fixes for pull requests using git worktrees?

Yes, you can draft test-backed fixes for pull requests using git worktrees. The process verifies npm test and npm run build checks pass before proposing any changes, ensuring mechanical and bounded fixes are safely isolated from the main branch.

How does triage handle contributor PRs that already address a CI failure?

Triage handles contributor PRs by reviewing whether an existing open pull request already addresses the detected CI failure. It follows a review-first workflow that reviews the existing PR instead of competing with it or drafting duplicate fixes.

Do I need GitHub CLI and npm test checks before proposing repository changes?

Yes, you need GitHub CLI access and must verify npm test and npm run build checks before proposing repository changes. These prerequisites ensure that drafted fixes are bounded, test-backed, and safe to apply to the mcpvault repository state.

What is the best way to dedupe repeated CI failure signals across daily maintenance runs?

The best way to dedupe repeated CI failure signals across daily maintenance runs is to persist state tracking and run history. Triage keeps open commitments visible so the next run resumes cleanly without re-processing identical repository findings.