triage-issue

Explore a codebase to identify root causes and draft GitHub issues with TDD-based fix plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage a bug or issue by exploring the codebase to identify the root cause and create a GitHub issue with a TDD-based fix plan, streamlining debugging and communication.

Core Features & Use Cases

  • Explore the codebase to locate where a bug manifests and trace its path.
  • Define a concrete TDD-based plan to fix the root cause and document it in a GitHub issue.
  • Use when users report problems, want to file issues, mention triage, or need structured remediation planning.

Quick Start

Describe the initial steps to start triaging a reported problem and generating a GitHub issue with a TDD 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 create a GitHub issue with a fix plan?

Issue triage involves exploring the codebase to trace the root cause of a bug, then generating a GitHub issue with a TDD-based fix plan and clear acceptance criteria to streamline debugging and communication.

What is the best way to plan a TDD-based fix for a reported bug?

A TDD-based fix plan documents the root cause of a bug in the codebase and outlines a structured, test-driven remediation strategy with clear acceptance criteria directly within a GitHub issue.

Can I use this triage workflow to investigate problems in any codebase?

Yes, this issue triage workflow applies to any codebase where users report problems, guiding code exploration to trace the bug's path, capture findings, and generate a structured GitHub issue for remediation.

How do I trace a bug to its root cause in my codebase?

Tracing a bug to its root cause involves systematically exploring the codebase to locate where the issue manifests, tracking its execution path, and capturing findings to draft a GitHub issue with a structured fix plan.

Do I need a GitHub repository to document a TDD fix plan for an issue?

Yes, you need a GitHub repository because the triage workflow captures codebase investigation findings and generates a public-facing GitHub issue containing the TDD-based fix plan and acceptance criteria.

When should I use a structured triage workflow for bug remediation?

You should use a structured triage workflow when users report problems or when you need to file new issues, ensuring debugging and communication are streamlined through a GitHub issue with clear acceptance criteria.