aif-fix

Diagnose bugs, plan fixes, modify code, and document with structured steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables developers to efficiently diagnose and resolve bugs or problems in codebases by providing structured workflows, detailed investigation steps, and clear guidance for fixes.

Core Features & Use Cases

  • Bug Diagnosis: Helps identify the root cause of errors, such as exceptions or incorrect behaviors, through investigation and analysis.
  • Fix Workflow: Guides the user through creating a step-by-step fix plan, including impact analysis, affected files, and risk assessments.
  • Automated Fix Application: Implements code fixes with mandatory logging for debugging and verification.
  • Test Suggestion: Recommends adding tests to prevent regressions, with support for creating test files based on the fix.
  • Patch Generation: Produces learning patches that document the issue, root cause, fix, and preventive measures.
  • Handoff Support: Integrates with external task management for status updates, plan sharing, and progress tracking.

Quick Start

Initiate a bug fix by describing the error or behavior, then choose whether to create a fix plan or fix immediately, following the structured workflows provided.

Frequently Asked Questions about aif-fix

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

FAQPage Schema
How do I diagnose a bug when I don't know the root cause?

To diagnose a bug with an unknown root cause, this Skill provides structured investigation and analysis workflows to systematically identify the source of exceptions or incorrect behaviors.

What's the best way to plan a code fix and assess its impact?

The best way to plan a code fix is using a structured fix workflow that guides you through step-by-step impact analysis, identifies affected files, and performs risk assessments before implementation.

How do I document a bug fix to prevent future regressions?

You can document a bug fix to prevent regressions by generating learning patches that detail the issue, root cause, applied fix, and preventive measures, alongside suggested test additions.

Can I track bug fix progress and share plans with external task management tools?

Yes, you can track bug fix progress and share plans through handoff support that integrates with external task management systems for status updates and progress tracking.

Should I create a fix plan or fix a bug immediately?

You should create a fix plan for complex bugs requiring impact analysis and risk assessment, while immediate fixes suit straightforward errors, both following structured workflows with mandatory logging.