fix

Fix codebase bugs with minimal evidence-based repairs and verification.

113|15|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/avibebuilder/claude-prime --skill fix-avibebuilder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/fix
Command: npx skills add https://github.com/avibebuilder/claude-prime --skill fix-avibebuilder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill restores intended behavior by applying focused, evidence-based repairs for bugs and runtime failures when there is enough diagnostic information to act. It prevents speculative changes by requiring a clear failing area, reproducible test, concrete error path, or prior diagnosis before making code modifications.

Core Features & Use Cases

  • Evidence-first repairs: Choose the minimal change that removes the root cause rather than masking symptoms.
  • Call-stack upstream rule: Trace crashes to the producer of bad data and fix the producer or caller, not just the crash site.
  • Verification and cleanup: Add or update durable tests, prove the failure is gone, exercise the repaired path, and remove temporary instrumentation once verified.
  • Use Case: Fix a failing unit test caused by an off-by-one error, repair an API 500 by correcting a malformed database query, or resolve a rendering bug by tracing bad state to its origin.

Quick Start

Provide the failing test, error logs, and a short description of expected behavior and ask the fix skill to implement the minimal code change that removes the root cause and add verification.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I fix a failing unit test caused by a code bug?

To fix a failing unit test, apply a minimal-scope change that removes the root cause rather than masking symptoms. Trace the crash to the producer of bad data via the call stack, verify the repair with matching tests, and remove temporary instrumentation once validated.

What is the best way to repair an API 500 error from a malformed database query?

Repairing an API 500 error requires evidence-based fixes: use the concrete error path and logs to identify the malformed query, apply a targeted correction to the codebase, and confirm the runtime fault is resolved through independent tester confirmation.

Do I need a reproducible test to diagnose and fix a runtime fault?

Yes, fixing runtime faults requires a clear failing area, reproducible test, concrete error path, or prior diagnosis before making code modifications. This diagnostic evidence prevents speculative changes and ensures the bugfix targets the actual root cause.

Why does my code crash downstream, and should I fix the crash site or the caller?

Code crashes downstream should be fixed at the producer of bad data or the caller, not just the crash site. The call-stack upstream rule traces bad state to its origin, ensuring the evidence-based repair resolves the root cause rather than the symptom.

How do I verify a bugfix and clean up temporary instrumentation after code repair?

Verify a bugfix by adding or updating durable tests to prove the failure is gone and exercise the repaired path. Once verification is complete through matching tests or independent confirmation, remove all temporary instrumentation used during debugging.