skills.rest
jnlanahan
jnlanahanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

triage

Triage user bug reports into evidence-backed hypotheses with file:line citations.

Updated Apr 30, 2026
Search Tags:#debugging#TDD#root cause analysis#bug report#incident response#codebase investigation#bug triage
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill triage-jnlanahan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/5-Validate-Triage
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill triage-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates slow, error-prone bug investigations by turning a vague “this is broken” report into an evidence-backed root-cause hypothesis, prioritized fixes, and a complete, ready-to-action bug report.

Core Features & Use Cases

  • End-to-end bug triage: Clarifies the repro goal, investigates the codebase, and documents findings in a consistent format.
  • Evidence-based root-cause hypothesis: Requires file:line citations and discourages guess-and-patch behavior.
  • Actionable outputs: Proposes at least two options (root fix plus workaround) and writes the bug report to .claude/bugs/<short-name>.md for later pickup by a teammate.
  • Workflow coverage: Replaces standalone bug-investigation, bug-report, and QA-session flows for faster handling of production or intermittent issues.

Quick Start

Ask the assistant to run /triage after you describe what you expected versus what happened and include any relevant error logs.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I investigate a vague bug report and find the root cause in my codebase?▼

Bug triage clarifies the reproduction goal, investigates the codebase, and builds an evidence-backed root-cause hypothesis with file:line citations. It transforms vague reports into a structured Markdown bug report, ensuring you address the actual defect.

What is the best way to fix an intermittent production issue without guessing?▼

Use evidence-based bug triage to discourage guess-and-patch behavior by requiring file:line citations for root-cause hypotheses. This process ensures your investigation of intermittent production issues relies on verifiable codebase evidence.

How do I write a bug report that includes TDD RED-GREEN plans for fixes?▼

Bug triage generates a complete Markdown bug report that proposes at least two fix options, including a root fix and a workaround, each accompanied by TDD RED-GREEN plans. The report is saved directly to .claude/bugs/.

Does bug triage work for debugging unclear user-reported issues?▼

Yes, bug triage is designed for debugging sessions where a user reports something is broken or requests investigation. It handles unclear production issues by clarifying the expected versus actual behavior before investigating the codebase.

How do I start a bug investigation session using triage?▼

Describe what you expected versus what happened, include any relevant error logs, and ask the assistant to run /triage. This triggers an end-to-end investigation that outputs a documented bug report with proposed fixes.

Related Skills

Explore More Software Engineering Skills→
pcasarettopcasaretto

bug-reproduction-validator

Reproduce reported software issues and classify them as bugs, environmental problems, or user errors.

Community
Advanced
OutlineDrivenOutlineDriven
5

triage-issue

Triage reported bugs and generate a RED-GREEN TDD fix plan as a GitHub issue artifact.

Official
Advanced
tankpkgtankpkg
1

@tank/bdd-issue-fixer

Automate GitHub issue resolution through BDD workflows and Gherkin scenarios.

Official
Advanced
mrkhachaturovmrkhachaturov

systematic-debugging

Guide engineers through phased root-cause investigation and evidence-based debugging.

Community
Advanced