triage-issue

Investigate reported bugs and produce root-cause analyses with TDD fix plans.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill triage-issue-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/triage-issue
Command: npx skills add https://github.com/softspark/ai-toolkit --skill triage-issue-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual overhead of diagnosing reported bugs by autonomously exploring the codebase to find root causes and producing a durable, test-driven fix plan ready to file as a GitHub issue.

Core Features & Use Cases

  • Deep repository diagnosis: Traces manifestation to code paths, examines related modules, and checks recent git history to identify root causes.
  • TDD-based remediation plan: Produces ordered RED→GREEN test cycles that verify behavior through public interfaces and outline minimal code changes.
  • Issue creation and handoff: Formats findings and the TDD plan into a GitHub issue using the gh CLI so engineering teams can act immediately.
  • Use Case: When a user reports a crash or incorrect behavior, run this Skill to autonomously locate the likely cause, design tests, and open a tracked issue with an actionable fix plan.

Quick Start

Invoke /triage-issue with a concise bug description to start an autonomous investigation and generate a TDD fix plan.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I automate bug triage and generate a TDD fix plan?

To automate bug triage, you provide a concise bug description to trigger an autonomous codebase investigation. This generates a root-cause analysis and a test-driven development fix plan formatted as a ready-to-file GitHub issue.

What is the best way to find a root cause for a reported software bug?

Finding a root cause for a software bug requires deep code exploration and git history review to trace the manifestation to specific code paths. This process autonomously examines related modules to identify the exact underlying issue.

How do I create GitHub issues for bug fixes directly from the command line?

Creating GitHub issues from the command line requires the gh CLI and repository read access. The triage process formats the root-cause analysis and TDD remediation plan into a tracked issue for immediate engineering handoff.

Does automated issue triage work with existing test-driven development workflows?

Automated issue triage integrates with test-driven development workflows by producing ordered RED to GREEN test cycles. These cycles verify behavior through public interfaces and outline minimal code changes required for the fix.

Can I use autonomous triage for software repositories without running shell commands?

Autonomous triage requires repository read access and the ability to run code searches and shell commands. Without these permissions, the deep code exploration and git history review needed to identify root causes cannot execute.