skills.rest
JGcode3675
JGcode3675COMMUNITY
Explore all skills by this author →
GitHub

fix-bug

Guide developers through a six-step bug diagnosis and fixing process.

Updated Aug 27, 2026
Search Tags:#testing#debug#diagnosis#reproduce#workflows#bug-fix
One-click install
npx skills add https://github.com/JGcode3675/gcs-os --skill fix-bug-jgcode3675
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/JGcode3675/gcs-os/tree/main/home/james/claude-config/skills/fix-bug
Command: npx skills add https://github.com/JGcode3675/gcs-os --skill fix-bug-jgcode3675

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic bug fixing workflow. Use when a bug is reported and needs diagnosis and fix. Accepts bug description as argument.

Core Features & Use Cases

  • Step-by-step debugging lifecycle, including Understand, Reproduce, Diagnose, Fix, Verify, and Document.
  • Encourages minimal, surgical fixes and robust verification across tests.

Quick Start

Provide a concise bug description to initiate the systematic debugging workflow.

Frequently Asked Questions about fix-bug

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

FAQPage Schema
How do I systematically debug and fix a software bug across a codebase?▼

To systematically debug and fix a software bug, follow a six-step workflow: Understand, Reproduce, Diagnose, Fix, Verify, and Document. This process enforces clear bug descriptions, targeted tests, and minimal patches.

What is the best workflow for diagnosing a reported bug and verifying the fix?▼

The best workflow for diagnosing a bug requires reproducing it first, then applying a surgical fix, and finally verifying the correction across tests. This structured approach prevents regression and ensures robust bug diagnosis.

How do I reproduce a bug from a description before attempting a code fix?▼

To reproduce a bug from a description, you must first understand the reported issue and then systematically isolate the conditions that trigger the fault. This reproduction step is mandatory before moving to diagnosis and patching.

Can I use a structured debugging process for any reported software bug?▼

Yes, you can apply a structured debugging process to any reported software bug. The workflow accepts a concise bug description as input and guides you through diagnosis and verification regardless of the underlying codebase.

Why should I write tests and minimal patches when fixing bugs?▼

Writing tests and applying minimal patches during bug fixing ensures surgical changes that do not introduce regressions. This workflow mandates robust verification to confirm the diagnosis and fix are isolated and correct.

When do I need a formal step-by-step process for bug diagnosis?▼

You need a formal step-by-step process for bug diagnosis when a reported issue requires systematic reproduction and verification to resolve. Applying a structured workflow ensures the fix is documented and validated across tests.

Related Skills

Explore More Software Engineering Skills→
CaneproCanepro

triage-issue

Diagnose bugs or regressions and produce a testable fix plan.

Community
Advanced
RheasilviaRheasilvia

test-driven-development

Enforce the Red-Green-Refactor cycle with automated tests via terminal.

Community
Advanced
DigitalCreationsCoDigitalCreationsCo
4

debugging-strategies

Identify and solve bugs using a structured debugging methodology.

Community
Advanced
Galaxy-DawnGalaxy-Dawn
5.1k

bug-detective

Diagnose and fix software errors through structured debugging workflows.

Community
Basic