skills.rest
nimadorostkar
nimadorostkarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bug-fix-protocol

Enforce test-driven development and root-cause analysis for bug resolution.

25|3|Updated Jul 14, 2026
Search Tags:#testing#debugging#regression#process#root-cause#bugfix
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill bug-fix-protocol-nimadorostkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-fix-protocol
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/development/bug-fix-protocol
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill bug-fix-protocol-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure modes of patching symptoms or fixing bugs without verification, ensuring that defects are resolved permanently and safely.

Core Features & Use Cases

  • Disciplined Workflow: Guides the agent through a mandatory sequence of reproduction, test creation, minimal fixing, and verification.
  • Regression Prevention: Encourages searching for sibling bugs and documenting the root cause to prevent future occurrences.
  • Use Case: When a production regression is reported, use this skill to ensure the agent writes a failing test case before attempting any code changes, guaranteeing the fix is verified and the root cause is addressed.

Quick Start

Apply the bug-fix-protocol to investigate and resolve the reported issue with the user authentication flow.

Frequently Asked Questions about bug-fix-protocol

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

FAQPage Schema
What is the best way to fix a production regression without patching symptoms?▼

Fixing a production regression requires a test-driven protocol that enforces issue reproduction, failing test creation, minimal code modification, and root-cause analysis to ensure the defect is resolved permanently and safely.

How do I enforce a test-driven bug resolution process for software maintenance?▼

Enforce a test-driven bug resolution process by following a mandatory workflow sequence: reproduce the reported issue, write a failing test case, apply a minimal code fix, and run comprehensive verification to prevent future regressions.

Why does writing a failing test case before code changes matter for debugging?▼

Writing a failing test case before debugging matters because it guarantees the defect is successfully reproduced and provides immediate verification once the minimal code fix is applied, ensuring the root cause is addressed.

Can I use this bug fixing protocol for hotfix scenarios?▼

Yes, you can use this bug fixing protocol for production hotfix scenarios, as it standardizes the end-to-end resolution process by requiring structured reproduction, minimal code modification, and comprehensive verification of the fix.

How to prevent sibling bugs when resolving a reported software defect?▼

Prevent sibling bugs during software defect resolution by searching for related failure modes after identifying the root cause, documenting the underlying issue, and applying regression testing to verify comprehensive fix coverage.

Related Skills

Explore More Software Engineering Skills→
jlissnerjlissner

grimoire-bug

Reproduce reported bugs with failing tests before implementing minimal fixes.

Community
Intermediate
first-flukefirst-fluke
218

debug-agent

Diagnose software bugs and propose minimal regression-tested fixes.

Official
Advanced
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced
SanderMullerSanderMuller
214

bug-fixing

Automates test-driven debugging workflows to isolate and fix defects in software projects.

Community
Intermediate