ai-factory.fix

Diagnose and fix software bugs with a logged, patch-based workflow.

1.1k|92|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-factory.fix
Source: https://github.com/lee-to/ai-factory/tree/main/skills/fix
Command: npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, logging-driven workflow to diagnose, fix, verify, and learn from bugs in codebases, ensuring fixes are traceable and testable.

Core Features & Use Cases

  • Deterministic debugging workflow: follows a defined sequence from problem understanding to verification.
  • Logging-first fixes: requires logging around the fix for traceability and learning.
  • Self-improvement through patches: automatically generates a patch document for future reference and learning.

Quick Start

Describe the bug, and I will guide you through a safe, logged fix.

Frequently Asked Questions about ai-factory.fix

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

FAQPage Schema
How do I automatically diagnose and fix software bugs with a traceable patch?

To diagnose and fix software bugs automatically, you describe the bug report and follow a deterministic, patch-based workflow. This process applies logging around the code fix to ensure traceability and generates a patch document for future reference.

What is the best way to add logging when fixing regressions and edge-case failures?

The best way to add logging when fixing regressions is through a logging-first debugging workflow. This requires mandatory logging around the applied code fix to ensure the resolution remains traceable and testable across languages and projects.

Can I use a structured debugging workflow for common bug reports across different programming languages?

Yes, you can use this structured debugging workflow for common bug reports across different programming languages. It follows a deterministic sequence from problem understanding to verification, applying safely during both software development and maintenance.

How do I generate a patch document after resolving a codebase bug?

To generate a patch document after resolving a codebase bug, the fix workflow automatically creates one as part of its output. This self-improvement mechanism records the diagnostic steps and code fix for learning and future reference.

Does automated bug fixing provide guidance for test coverage?

Yes, automated bug fixing provides guidance for test coverage as part of its deterministic workflow. After diagnosing and applying a code fix, the process includes steps to verify the resolution and advises on necessary test coverage.

Why should I use a logging-driven workflow instead of applying a direct code fix?

A logging-driven workflow ensures your code fix is traceable and testable, unlike direct ad-hoc fixes. It follows a deterministic sequence from problem understanding to verification, capturing mandatory logs and generating a patch for future reference.