skills.rest
CinnamonfirJ
CinnamonfirJCOMMUNITY
Explore all skills by this author →
GitHub

triage-issue

Convert bug reports into root-cause diagnoses and GitHub issues with TDD repair plans.

Updated Aug 27, 2026
Search Tags:#TDD#root cause analysis#codebase investigation#test planning#red green refactor#bug triage#GitHub issue creation
One-click install
npx skills add https://github.com/CinnamonfirJ/task-hub-webapp --skill triage-issue-cinnamonfirj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/CinnamonfirJ/task-hub-webapp/tree/main/skills/triage-issue
Command: npx skills add https://github.com/CinnamonfirJ/task-hub-webapp --skill triage-issue-cinnamonfirj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly convert a vague bug report into a well-scoped investigation, root-cause analysis, and an actionable GitHub issue with a TDD-based repair plan.

Core Features & Use Cases

  • Root-cause investigation: Locates where the bug manifests, the involved code path, and the underlying reason it fails.
  • TDD fix planning: Produces an ordered RED-GREEN cycle list that specifies behavior-focused tests and minimal code changes.
  • Hands-off issue creation: Generates a GitHub issue using a structured template without requiring the user’s review before creation.
  • Use Case: When a user notices unexpected behavior in task management, bidding, chat, identity verification, or wallet/escrow flows, you can triage the issue to decide what should change and how to prove it with tests.

Quick Start

Use the triage-issue skill to investigate the reported problem and automatically create a GitHub issue with a TDD 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 convert a vague bug report into a root-cause analysis and fix plan?▼

To convert a bug report into a root-cause analysis and fix plan, triage the issue by exploring the codebase to locate the failure path, identify the underlying reason, and generate a GitHub issue containing a behavior-driven TDD repair plan.

How does TDD fix planning work for investigating regressions in API responses?▼

TDD fix planning for API regressions works by producing an ordered RED-GREEN cycle list that specifies behavior-focused tests and minimal code changes needed to prove the repair, using observable outcomes rather than implementation details.

Can I automatically create a GitHub issue with a TDD repair plan without manual review?▼

Yes, you can automatically create a GitHub issue with a TDD repair plan without manual review. The triage process generates the issue using a structured template containing the root-cause diagnosis and ordered test cycles hands-off.

What is the best way to plan a TDD fix for missing features in UI and wallet flows?▼

The best way to plan a TDD fix for UI and wallet flows is to investigate the reported problem to decide what should change, locate the involved code path, and output an ordered RED-GREEN cycle list proving the fix with observable outcomes.

Does this triage approach work for investigating design flaws across related modules?▼

Yes, this triage approach works for investigating design flaws across related modules. It applies to software engineering teams investigating regressions, missing features, or design flaws across UI, API responses, and connected modules.

Why does codebase investigation require evidence-based root-cause identification before writing tests?▼

Codebase investigation requires evidence-based root-cause identification before writing tests to ensure the ordered RED-GREEN cycle list targets the actual failure path and underlying reason rather than guessing the implementation details.

Related Skills

Explore More Software Engineering Skills→
FlintmereFlintmere

fix-bug

Reproduce reported defects in Flintmere's codebase and validate fixes with regression tests.

Official
Advanced
sandgardenhqsandgardenhq
130

test-driven-development

Write failing tests before production code using a red-green-refactor cycle.

Official
Intermediate
tankpkgtankpkg
1

@tank/bdd-issue-fixer

Automate GitHub issue resolution through BDD workflows and Gherkin scenarios.

Official
Advanced
rsmdtrsmdt
381

debugging-methodology

Guide hypothesis-driven debugging with evidence-based root-cause analysis.

Community
Advanced