aif-fix

Identify and fix codebase bugs with plan-first or immediate patch workflows.

83|5|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-fix-artemyurov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-fix
Source: https://github.com/ArtemYurov/TomoBar/tree/main/.claude/skills/aif-fix
Command: npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-fix-artemyurov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates structured bug-fix workflows for codebases, guiding users through either an immediate fix or a plan-first approach, and ensuring traceability with plans and patches.

Core Features & Use Cases

  • Plan-first: Create a FIX_PLAN.md before applying any change to outline root cause, affected files, and steps.
  • Immediate fix: Execute a targeted fix with built-in logging and suggested tests, then generate a self-contained patch.
  • Patch & history: Automatically generate a patch under .ai-factory/patches with a timestamp for future reference.
  • Audit & safety: Enforce minimal changes, thorough logging, and test suggestions to prevent regressions.

Quick Start

Provide a bug description or error message to start the AI-assisted fix workflow.

Frequently Asked Questions about aif-fix

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

FAQPage Schema
How do I fix bugs in a codebase with an AI-assisted workflow?

To fix bugs in a codebase using an AI-assisted workflow, you can provide a bug description or error message to trigger either a plan-first approach or an immediate patch.

What's the best way to plan a bug fix before applying code changes?

The best way to plan a bug fix before applying changes is using a plan-first approach that generates a FIX_PLAN.md outlining the root cause, affected files, and required steps.

How do I ensure my code debugging patches are auditable and prevent regressions?

You can ensure code debugging patches are auditable and prevent regressions by enforcing minimal scope changes, adding thorough logging, and generating suggested tests alongside the patch.

How does a plan-first bug fix workflow handle patch history?

A plan-first bug fix workflow handles patch history by automatically generating a self-contained patch under .ai-factory/patches with a timestamp for future reference and traceability.

Can I execute an immediate code fix without creating a separate plan first?

Yes, you can execute an immediate targeted code fix without a separate plan, which applies built-in logging and suggested tests before automatically generating a timestamped patch.

Why does my AI bug fix workflow need a FIX_PLAN.md?

An AI bug fix workflow needs a FIX_PLAN.md to establish traceability by explicitly defining the root cause, affected files, and resolution steps before any code is modified.