skills.rest
caezium
caeziumCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

triage-issue

Explore codebases to diagnose root causes and draft TDD fix plans.

2|Updated Apr 25, 2026
Search Tags:#planning#tdd#debugging#issue#triage#bug
One-click install
npx skills add https://github.com/caezium/skills --skill triage-issue-caezium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/caezium/skills/tree/main/triage-issue
Command: npx skills add https://github.com/caezium/skills --skill triage-issue-caezium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams systematically triage bugs by exploring the codebase to identify root causes and generate a structured GitHub issue with a TDD-based fix plan.

Core Features & Use Cases

  • Guided problem capture and scope definition for user-reported bugs.
  • Deep codebase exploration to trace the bug to its root cause and related patterns.
  • Creation of a concise GitHub issue with a RED-GREEN cycle-based fix plan to guide implementation.
  • Supports documenting tests, acceptance criteria, and a clear remediation path for maintainers.

Quick Start

Capture a bug description and start exploration to identify the root cause, then draft 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 bugs and find their root cause in my codebase?▼

To triage bugs effectively, you need a structured plan that explores the codebase to identify root causes. This approach guides systematic investigation to trace reported issues and related patterns before drafting a fix.

How do I create a GitHub issue with a TDD-based fix plan for a bug?▼

Creating a GitHub issue with a TDD-based fix plan involves documenting RED-GREEN cycles, acceptance criteria, and a clear remediation path. This structure guides maintainers through writing failing tests first, then implementation.

What is the best way to investigate user-reported issues systematically?▼

The best way to investigate user-reported issues is through guided problem capture and scope definition. Deep codebase exploration then traces the bug to its root cause, ensuring a disciplined workflow before any code changes.

Can I use a structured triage workflow for internal bugs without external dependencies?▼

Yes, a structured triage workflow applies to both user-reported issues and internal bugs. It operates without external dependencies, enforcing a disciplined capture, exploration, and root-cause analysis process.

What should be included in a bug fix plan to guide implementation?▼

A bug fix plan should include documented tests, acceptance criteria, and a clear remediation path. Structuring it with RED-GREEN cycles ensures maintainers write failing tests first, then implement the passing code.

Why does my bug triage process fail to identify the actual root cause?▼

Bug triage often fails to identify root causes when lacking deep codebase exploration to trace related patterns. A disciplined workflow enforcing capture, exploration, and analysis is required to avoid missing underlying issues.

Related Skills

Explore More Software Engineering Skills→
jMertajMerta
130

bug-triage

Convert ambiguous bug reports into reproducible repros, root-cause explanations, and minimal fixes.

Community
Advanced
drshailesh88drshailesh88

triage-issue

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

Community
Advanced
Imad-OuteImad-Oute
2

mh-cto-sdlc-tdd-session

Enforce the RED-GREEN-LOOP cycle for iterative story implementation.

Community
Advanced
arvindbattulaarvindbattula

triage

Identify bug root causes and generate GitHub issues with TDD fix plans.

Community
Advanced