triage

Classify GitHub issues and pull requests with root cause analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill triage-mferris77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/triage
Command: npx skills add https://github.com/mferris77/SpringBoard --skill triage-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual effort of triaging GitHub issues and pull requests by providing structured classification, targeted code searches, root cause analysis, and actionable review recommendations so maintainers can decide or act faster.

Core Features & Use Cases

  • Issue intake and classification: find untriaged issues, detect stale reports, and assign type and severity.
  • PR review and analysis: read diffs, classify PRs, detect regressions, check cross-platform and convention compliance, and produce file:line findings.
  • Investigation and resolution plans: search the codebase for error text or stack traces, perform root cause analysis, draft fixes or auto-fix handoffs, and prepare structured comments for maintainers.

Quick Start

Run the triage skill with a command like /triage to classify open issues and generate investigation reports.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate GitHub issue triage and root cause analysis?

Automating GitHub issue triage involves classifying untriaged reports and performing root cause analysis by searching repository code for stack traces or error text. This process identifies problem origins and drafts actionable fix branches or comments for maintainers to act on faster.

What is the best way to automate pull request review and detect regressions?

Automating pull request review reads code diffs to classify PRs, detect regressions, and check convention compliance. It generates file:line findings and structured review recommendations, reducing manual code review effort by pinpointing exact locations of potential issues.

How do I classify stale GitHub issues and assign severity automatically?

Classifying stale GitHub issues and assigning severity requires analyzing open repository reports to detect inactivity and categorize problem types. This structured intake process organizes the issue backlog by identifying untriaged reports and labeling their priority.

Do I need gh CLI authentication to run automated code review and issue triage?

Yes, you need gh CLI authentication and repository access to perform automated code review and issue triage. Operating on GitHub issues and pull requests requires running repository code searches, diffs, and remote git commands through the authenticated command-line interface.

Can I generate fix branches and draft comments for maintainers from a GitHub issue?

Generating fix branches and drafting comments for maintainers from a GitHub issue uses repository code searches to locate root causes. It prepares structured investigation reports and auto-fix handoffs so maintainers can review and act on proposed resolutions immediately.