skills.rest
kaiohenricunha
kaiohenricunhaCOMMUNITY
Explore all skills by this author →
𝕏@kaiohenricunhaGitHub

fix-with-evidence

Enforce an evidence-gated workflow for bug fixes with reproduction testing and regression detection.

Updated Apr 14, 2026
Search Tags:#debugging#pull request#software development#bug fixing#regression prevention#test validation#evidence-based workflow
One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill fix-with-evidence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-with-evidence
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/fix-with-evidence
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill fix-with-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unvalidated, regression-prone bug fixes by enforcing a strict, evidence-gated workflow that ensures every fix is properly tested and documented before submission.

Core Features & Use Cases

  • Gated 4-Phase Workflow: Enforces Reproduce → Fix → Verify → PR steps, with each phase requiring explicit validation before proceeding to the next.
  • Mandatory Reproduction Testing: Requires a failing test to confirm the bug exists before any fix work begins, eliminating guesswork and unfounded changes.
  • Regression Detection: Runs the full project test suite and uses git stash to distinguish pre-existing failures from new regressions introduced by the fix.
  • Use Case: Ideal for software developers fixing bugs in any codebase, ensuring fixes are minimal, validated, and accompanied by clear, structured PR documentation.

Quick Start

Use the fix-with-evidence skill to resolve the intermittent API timeout bug reported in issue #127.

Frequently Asked Questions about fix-with-evidence

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

FAQPage Schema
How do I prevent regressions when fixing bugs in a software codebase?▼

Preventing regressions during bug fixing requires running the full test suite and using git stash to distinguish pre-existing failures from new issues. This evidence-gated workflow ensures every fix is validated against the entire project suite before submission.

What is an evidence-based workflow for software bug fixing?▼

An evidence-based bug fixing workflow enforces a strict four-phase loop: Reproduce, Fix, Verify, and PR. It requires explicit validation at each phase, starting with a mandatory failing test to confirm the bug exists before any code changes begin.

How to create a pull request for a bug fix with proper validation?▼

Creating a validated pull request for a bug fix requires structured documentation after completing the reproduction, fixing, and full test suite verification phases. This process ensures the PR contains evidence that the defect was resolved without unintended side effects.

Do I need a failing test before starting to fix a reported defect?▼

Yes, a failing test is a mandatory prerequisite to confirm the reported defect exists. Writing a reproduction test before making any code changes eliminates guesswork and ensures you are fixing the actual issue rather than applying unfounded changes.

Can I use this bug fixing workflow for any software development project?▼

Yes, this workflow applies to software development tasks where developers resolve reported bugs, issues, or defects in any codebase. It is ideal for ensuring fixes are minimal, properly validated, and accompanied by clear PR documentation.

Best way to verify a bug fix does not break existing test suites?▼

The best way to verify a bug fix is to run the full project test suite and use git stash to detect pre-existing failures. This regression detection method isolates your changes and confirms they do not introduce unintended side effects.

Related Skills

Explore More Software Engineering Skills→
anorthamanortham

bug-detective

Diagnose bugs through guided reproduction, tracing, and test-driven verification.

Community
Advanced
1J6K211J6K21

code-review-and-quality

Review code changes across correctness, readability, architecture, security, and performance.

Community
Intermediate
Exia-thdExia-thd

debugger

Diagnoses software bugs and system failures from root cause to fix with regression tests.

Community
Advanced
rsmdtrsmdt
381

debugging-methodology

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

Community
Advanced