bug-fix

Analyze bug reports into reproduction steps, root-cause findings, and specification-gap assessments.

18|Updated Feb 14, 2020
One-click install
npx skills add https://github.com/subroh0508/colormaster --skill bug-fix-subroh0508
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/bug-fix
Command: npx skills add https://github.com/subroh0508/colormaster --skill bug-fix-subroh0508

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a bug report into a clear reproduction plan, root-cause analysis, and specification-gap assessment, so teams can move from symptom to actionable planning without jumping into implementation too early.

Core Features & Use Cases

  • Reproduction Analysis: Breaks down the report into observed behavior, expected behavior, environment details, and repeatable steps.
  • Root Cause Investigation: Uses code context, logs, git blame, and history to identify direct and indirect causes.
  • Spec Gap Detection: Checks existing specifications and creates follow-up documentation when the behavior is undefined or the spec is incomplete.
  • Plan-Ready Handoff: Produces a plan-oriented summary with acceptance criteria and testing ideas for the implementation workflow.
  • Use Case: A QA report says a UI flow fails only on certain devices; this Skill isolates the reproduction path, narrows the likely cause, and prepares the handoff for the fix team.

Quick Start

Share the bug report, environment details, logs, and related code context, and I will return a reproduction analysis, root-cause findings, and a plan-ready handoff summary.

Frequently Asked Questions about bug-fix

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

FAQPage Schema
How do I analyze a bug report to find the root cause and reproduction steps?

To analyze a bug report for root cause, you break down the report into observed behavior, expected behavior, and environment details to establish repeatable reproduction steps. This process uses code context, logs, and git blame tracing to isolate direct and indirect causes before delegating the fix.

What is the best way to prepare a bug triage handoff for the implementation team?

Preparing a bug triage handoff requires generating a plan-oriented summary with acceptance criteria and regression testing ideas. This ensures the implementation team receives structured reproduction analysis and root-cause findings without needing to jump into code editing early.

How do I detect specification gaps from an incident report?

Detecting specification gaps from an incident report involves checking existing specifications against the reported undefined behavior. When the spec is incomplete, the analysis creates follow-up documentation to align the observed behavior with implementation boundaries.

Can I use git blame to trace indirect causes during incident triage?

You can use git blame to trace indirect causes during incident triage by analyzing code history and logged evidence. This helps identify the specific implementation boundaries and code context that contributed to the reported defect.

Does this bug triage workflow edit code directly or generate a plan-only handoff?

This bug triage workflow generates a plan-only handoff and does not edit code directly. It requires alignment with existing specifications and logged evidence to ensure fixes are delegated to the implementation workflow with clear acceptance criteria.