triage-issue

Diagnose user-reported bugs and generate tracker issues with TDD fix plans.

12|2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/alexandrbasis/claudops --skill triage-issue-alexandrbasis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/triage-issue
Command: npx skills add https://github.com/alexandrbasis/claudops --skill triage-issue-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate a reported bug, identify the root cause, and convert it into a durable tracker issue with a TDD-based fix plan. This approach minimizes user questions and ensures a clear handoff to later steps without applying the fix.

Core Features & Use Cases

  • Exploration-based diagnosis using the Explore agent to locate the bug's location and affected code paths.
  • Generate a TDD-based fix plan organized as RED-GREEN cycles that describe step-by-step testing and minimal code changes.
  • Create a tracker issue (Linear or GitHub) with a clear problem statement, root-cause analysis, and acceptance criteria for handoff to /si.
  • Produce a durable artifact suitable for audit and future reference, independent of the current code layout.
  • NOT for interactive debugging; focuses on documentation and planning for future work.

Quick Start

Triage the reported bug and file a tracker issue with a TDD-based 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 triage a reported bug into a structured issue with a TDD fix plan?

To triage a reported bug into a structured issue, you identify the root cause and generate a durable tracker issue with a TDD-based RED-GREEN fix plan. This produces a handoff-ready artifact for Linear or GitHub.

Can I automatically create GitHub or Linear issues from a bug report?

Yes, you can create GitHub or Linear issues from a bug report by applying non-interactive triage to diagnose the problem. The output is a tracker issue containing a problem statement, root-cause analysis, and acceptance criteria.

What is the RED-GREEN TDD cycle in issue tracking and bug triage?

The RED-GREEN TDD cycle in issue tracking organizes a bug fix plan into steps for writing failing tests first, then making minimal code changes to pass them. This ensures a clear, structured handoff for later implementation.

Does this bug triage process apply the fix immediately during exploration?

No, this bug triage process does not apply the fix immediately. It uses an exploration phase to gather context and locate affected code paths, focusing solely on documentation and planning for future work.

When should I use non-interactive bug triage instead of interactive debugging?

Use non-interactive bug triage when you need to file issues for later fixes without applying changes immediately. It is designed for creating durable, handoff-ready artifacts rather than resolving problems through real-time interactive debugging.