fix-bugs

Diagnoses and fixes bugs from error messages or failing tests, then verifies solutions by rerunning them.

9|3|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/indoor47/memfun --skill fix-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-bugs
Source: https://github.com/indoor47/memfun/tree/main/skills/fix-bugs
Command: npx skills add https://github.com/indoor47/memfun --skill fix-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying, diagnosing, and fixing bugs within a codebase, ensuring code quality and stability.

Core Features & Use Cases

  • Root Cause Analysis: Systematically traces bugs to their origin using error messages, stack traces, and code behavior.
  • Targeted Fixes: Applies minimal, correct code changes to resolve identified issues.
  • Verification: Runs tests and reproduces errors to confirm fixes and prevent regressions.
  • Use Case: When a critical bug is reported in production, this Skill can be invoked with the error message to automatically locate the faulty code, apply a fix, and verify its resolution, minimizing downtime.

Quick Start

Use the fix-bugs skill to resolve the issue described by the error message 'KeyError: "user_id"'.

Frequently Asked Questions about fix-bugs

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

FAQPage Schema
How do I fix a bug from an error message and stack trace automatically?

To fix a bug from an error message, the system searches the codebase to identify root causes using the stack trace, applies targeted code repairs, and verifies the fix by running tests. It explains what was wrong and how the code was repaired.

What is the best way to find a root cause from a failing test?

Finding a root cause from a failing test involves systematically tracing the failure back to its origin. The system analyzes the test output, searches the codebase for the faulty logic, proposes a minimal correction, and reproduces the error to verify resolution.

How does code repair work when diagnosing production bugs?

Code repair for production bugs works by taking the reported error, locating the faulty code, and applying minimal changes to resolve the issue. It then runs tests to confirm the fix works and prevent regressions, minimizing downtime.

Can I resolve a KeyError using natural language bug descriptions?

Yes, you can resolve a KeyError using natural language bug descriptions. The system interprets the description, searches the codebase to locate the missing key reference, applies a targeted fix, and verifies the resolution by reproducing the original error.

What are the limitations of automated debugging and verification?

Automated debugging and verification relies on searching the existing codebase and running available tests to confirm fixes. It may not resolve issues lacking clear error messages, stack traces, or failing tests, and cannot fix bugs in dependencies outside the searched codebase.