triage-issue

Explore codebases to diagnose bugs and draft TDD-based fix plans.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/paialex/ai-skills-bank --skill triage-issue-paialex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/paialex/ai-skills-bank/tree/main/mattpocock_skills/deprecated/triage-issue
Command: npx skills add https://github.com/paialex/ai-skills-bank --skill triage-issue-paialex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage a bug or issue by exploring the codebase to identify root causes, then create a GitHub issue with a TDD-based fix plan. Use when a user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

Core Features & Use Cases

  • Guided problem capture to describe the issue and expected behavior.
  • Systematic exploration and diagnosis using an Explore workflow to trace the failure path and related code.
  • Concrete TDD-based fix plan outlining RED-GREEN cycles, tests, and acceptance criteria.
  • Structured GitHub issue creation to document findings, rationale, and next steps.
  • Suitable for user-reported bugs, regressions, and ambiguous failures requiring planning and coordination.

Quick Start

Provide a concise problem description and begin the triage workflow to surface root cause and 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 a bug and find its root cause in my codebase?

To triage a bug, you explore the codebase to trace the failure path, diagnose the root cause, and document a structured fix plan. This triage workflow captures the problem, expected behavior, and rationale for the repair strategy.

How do I create a TDD-based fix plan for a user-reported issue?

A TDD-based fix plan outlines RED-GREEN cycles, specific tests, and acceptance criteria for the bug. It guides you from reproducing the issue to drafting a durable fix strategy that ensures the codebase regression is resolved.

What's the best way to document a postmortem investigation for code repairs?

Documenting a postmortem investigation involves creating a structured GitHub issue that records findings, rationale, and next steps. This captures the failure path exploration and the TDD-based fix plan for future coordination.

Can I use a triage workflow for ambiguous failures and regression planning?

Yes, a triage workflow is suitable for ambiguous failures and regressions requiring planning. It systematically captures the problem, traces related code, and drafts a durable fix strategy with clear acceptance criteria.

Do I need a specific testing framework to draft a TDD fix plan?

No specific testing framework is required to draft a TDD fix plan. The workflow specifies the RED-GREEN cycles, tests, and acceptance criteria needed to reproduce and diagnose the issue across projects.

Why does exploring the codebase help when I want to file an issue for a bug?

Exploring the codebase helps file an issue by tracing the failure path to identify root causes. This systematic diagnosis ensures the resulting GitHub issue contains accurate findings and a durable TDD-based fix plan.