aif-fix

Investigate codebases, implement fixes with logging, and generate self-improvement patches.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/marinkobabic/dario-shop --skill aif-fix-marinkobabic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-fix
Source: https://github.com/marinkobabic/dario-shop/tree/main/.claude/skills/aif-fix
Command: npx skills add https://github.com/marinkobabic/dario-shop --skill aif-fix-marinkobabic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of debugging broken code by providing a structured, repeatable workflow for identifying root causes and applying fixes. It handles everything from simple null reference errors to complex API issues, ensuring no fix is applied without proper logging and test coverage.

Core Features & Use Cases

  • Dual Mode Operation: Choose between immediate fixes for urgent issues or a plan-first approach for complex bugs requiring review.
  • Handoff Integration: Seamlessly integrates with Handoff mode for autonomous bug fixing in agent workflows, including status tracking and plan annotations.
  • Self-Improving: Automatically creates patch files documenting root causes and prevention strategies, building a knowledge base for future fixes.
  • Use Case: Imagine your e-commerce API returns empty arrays for authenticated users. Use this Skill to trace the query logic, identify the incorrect filter, apply the fix with logging, and generate a patch documenting the root cause.

Quick Start

Use the aif-fix skill to fix the bug where the admin panel crashes when editing products with missing image references.

Frequently Asked Questions about aif-fix

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

FAQPage Schema
How do I fix codebase bugs through structured root cause analysis?

Fixing codebase bugs through structured root cause analysis involves reading project configuration files, analyzing code patterns, and implementing modifications with logging. This systematic approach ensures fixes address the actual underlying issue.

What is the best way to debug an API returning empty arrays for authenticated users?

Debugging an API returning empty arrays requires tracing query logic to identify incorrect filters and applying code repair with logging. A structured debugging workflow traces the data flow from authentication through the query execution to pinpoint the faulty logic.

Can I use a plan-first approach for complex bug fixing instead of immediate code repair?

Yes, you can use a plan-first approach for complex bug fixing instead of immediate code repair. Dual mode operation allows you to choose between urgent immediate fixes or generating a structured plan for complex bugs requiring review before modification.

Does this debugging workflow support generating patch files for knowledge retention?

Yes, this debugging workflow supports generating patch files for knowledge retention. It automatically creates patch files documenting root causes and prevention strategies, building a knowledge base for future code repair and self-improvement.

When should I not use an immediate fix for software engineering debugging?

You should not use an immediate fix for software engineering debugging when facing complex bugs requiring review. In these cases, a plan-first approach is better to ensure proper error resolution and code quality maintenance without unintended side effects.