triage-issue

Diagnose bug root causes and create GitHub issues with TDD-based fix plans.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill triage-issue-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/triage-issue
Command: npx skills add https://github.com/lfuuu/claude-rules --skill triage-issue-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug is reported, developers often jump straight to patching symptoms without understanding the root cause, or they file vague issues that lack actionable fix plans. This Skill automates the investigation: it explores the codebase to find the root cause, then creates a GitHub issue containing a structured TDD-based fix plan. ## Core Features & Use Cases - Autonomous codebase investigation: Uses an Explore subagent to trace execution paths, inspect related tests, review recent git history, and identify the root cause rather than the symptom. - TDD fix planning: Produces an ordered list of RED-GREEN cycles where each test verifies behavior through public interfaces, keeping the plan resilient to future refactors. - GitHub issue creation: Files the issue directly via gh issue create using a structured template covering the problem, root cause analysis, TDD plan, and acceptance criteria. - Use Case: A user reports "the export button returns empty CSVs". The Skill traces the export flow, discovers the query filters out valid rows, and files an issue with a three-cycle RED-GREEN plan and acceptance criteria. ## Quick Start Ask the assistant to triage the bug you observed and file a GitHub issue with a TDD fix plan, providing a one-sentence description of the problem.

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 bug and create a GitHub issue automatically?

Describe the observed problem in one sentence and invoke the triage workflow. It explores the codebase to find the root cause, designs a TDD fix plan, and creates the issue with gh issue create without asking for further confirmation.

What does a TDD-based fix plan look like in a bug report?

It is a numbered list of RED-GREEN cycles: each RED step defines a test capturing the broken behavior through public interfaces, and each GREEN step describes the minimal code change to pass it. A final refactor step may follow.

Does this workflow require the GitHub CLI?

Yes, issue creation uses the gh issue create command, so the GitHub CLI must be installed and authenticated. Codebase exploration and planning work without it, but filing the issue does not.

Why does the issue template avoid file paths and line numbers?

The plan describes modules, behavior, and contracts instead of implementation details so the issue stays accurate after large refactors. Tests target observable outcomes like API responses and UI state rather than internal structure.

When should I not use automated bug triage?

Avoid it when the problem cannot be reproduced or described at all, or when the fix requires product decisions rather than code changes. The workflow assumes a concrete observable defect in an explorable codebase.