issue-triage

Guide codebase exploration to uncover root causes and prepare TDD fix plans.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mia-cx/.agents --skill issue-triage-mia-cx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/mia-cx/.agents/tree/main/skills/issue-triage
Command: npx skills add https://github.com/mia-cx/.agents --skill issue-triage-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage bugs and issues by guiding codebase exploration to uncover root causes and prepare a TDD-based fix plan.

Core Features & Use Cases

  • Identify where a bug manifests, map the code path, and determine root cause.
  • Propose a concrete TDD-based fix plan with RED-GREEN cycles and a GitHub issue.
  • Create detailed issue descriptions that clearly communicate the problem, root cause, and test plan for maintainers.

Quick Start

Describe the problem to the agent and begin a hands-off triage workflow to identify root causes and draft a TDD fix plan.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I triage a bug in my codebase and identify the root cause?

To triage a bug, you need to systematically explore the codebase to map the code path where the failure manifests. This process uncovers the root cause by investigating entry points and related modules to determine the exact corrective actions required.

What's the best way to create a TDD-based fix plan for a reported GitHub issue?

Creating a TDD-based fix plan involves defining testable outcomes through public interfaces and structuring the resolution into deterministic RED-GREEN cycles. This approach prepares a precise correction workflow that can be attached directly to a GitHub issue.

Can I draft GitHub issues with a structured fix plan automatically from a bug report?

Yes, you can generate detailed GitHub issue descriptions directly from a bug report. The output clearly communicates the identified problem, the uncovered root cause, and the proposed test plan to maintainers for actionable resolution.

How do I prepare a TDD fix plan when triaging issues across multiple repositories?

Triage across multiple repositories requires a deterministic workflow that guides the investigation of failure modes and entry points within each specific codebase. This yields a structured fix plan with RED-GREEN cycles tailored to the targeted module.

Does issue triage require a specific testing framework to implement the RED-GREEN cycles?

Issue triage focuses on defining testable outcomes through public interfaces rather than mandating a specific testing framework. The generated fix plan outlines the deterministic RED-GREEN workflow but relies on your existing environment for execution.