fix-verified

Fix confirmed bugs at root cause with evidence and regression guards.

Updated Jun 22, 2026

Search Tags:#software development #root cause analysis #bug fixing #verification #evidence-based

Ready to run

npx skills add https://github.com/skylarsabo/code-ops --skill fix-verified

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-verified
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/rigor/skills/fix-verified
Command: npx skills add https://github.com/skylarsabo/code-ops --skill fix-verified

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill is used when confirmed bugs exist and you want them fixed at root cause with proof. It ensures that each confirmed bug is fixed with evidence of its root cause.

Core Features & Use Cases

Root Cause Fixes: Fix bugs at their root cause, not just symptoms.
Evidence-Based: Ensures that each fix is backed by reproducible evidence.
Verification-First Methodology: Follows a strict verification-first methodology with evidence tiers, disconfirmation pass, and root-cause-over-symptom approach.
Regression Guard: Adds regression guards to prevent future occurrences of the same bug.

Quick Start

Run the fix-verified skill to automatically address confirmed bugs at root cause with proof, ensuring a robust solution.

Frequently Asked Questions about fix-verified

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

FAQPage Schema

How do I fix confirmed software bugs at the root cause instead of just patching symptoms?▼

Root cause bug fixing requires identifying the underlying issue and verifying the solution with reproducible evidence. This Skill automates that verification-first methodology, ensuring each confirmed bug is resolved at its source rather than just treating symptoms.

What is evidence-based bug fixing and how does it prevent regressions?▼

Evidence-based bug fixing validates root causes through reproducible proof and tiered verification before applying a patch. It adds regression guards to your test suite, preventing the same confirmed software defects from reoccurring in future development cycles.

Do I need a specific file or test suite to automate root cause analysis for confirmed bugs?▼

Yes, root cause analysis automation requires a FINDINGS_REGISTER.md file containing confirmed bug details and an existing test suite for regression checks. These inputs provide the verified defect context and validation framework needed to generate proven fixes.

What's the best way to ensure my bug fixes are proven before merging code changes?▼

Proven bug fixes require a verification-first methodology with evidence tiers and a disconfirmation pass. This approach validates that your fix addresses the root cause over symptoms, providing concrete proof that the confirmed defect is resolved.

When should I use a verification-first approach for software bug fixing?▼

Use a verification-first approach for software bug fixing when working with confirmed defects where proven solutions are critical. It is designed for development workflows demanding evidence-based root cause resolution rather than speculative symptom patching.

Why does my automated bug fix still fail regression checks after patching the symptom?▼

Automated bug fixes fail regression checks when they patch symptoms instead of the root cause. A verification-first methodology with evidence-based validation and a disconfirmation pass ensures the underlying defect is actually resolved before closing the ticket.