aif-fix

Diagnose codebase bugs and generate a FIX_PLAN.md for guided fixes.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/VeronikaVashkevich/job-tracking-app --skill aif-fix-veronikavashkevich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-fix
Source: https://github.com/VeronikaVashkevich/job-tracking-app/tree/main/.opencode/skills/aif-fix
Command: npx skills add https://github.com/VeronikaVashkevich/job-tracking-app --skill aif-fix-veronikavashkevich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to diagnose and fix bugs in a codebase, guiding users from problem intake to verifiable patches with mandatory logging and test suggestions.

Core Features & Use Cases

  • Immediate fix or plan-first approach to bug resolution.
  • Auto-generates a FIX_PLAN.md when a plan is chosen, then follows it step-by-step.
  • Enforces mandatory logging around fixes and suggests tests to prevent regressions.
  • Supports iterative cycles with self-improvement patches for knowledge sharing.

Quick Start

Describe the bug or error message, then choose a mode with AskUserQuestion and proceed.

Frequently Asked Questions about aif-fix

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

FAQPage Schema
How do I plan and fix bugs in my codebase with guardrails?

A bug fix workflow distinguishes between applying an immediate patch and creating a step-by-step FIX_PLAN.md. Both paths enforce mandatory logging and suggest tests to prevent future regressions across your codebase.

How do I generate a fix plan for a complex codebase bug?

You can generate a fix plan by selecting the plan-first mode, which automatically creates a FIX_PLAN.md file. The system then follows this plan step-by-step to apply required patches and resolve the bug.

Does fixing bugs with a structured plan require writing tests?

A structured bug fix workflow suggests tests to prevent regressions and enforces mandatory logging around applied patches. This ensures your codebase remains stable and verifiable after resolving the issue.

What is the best way to document a bug fix for knowledge sharing?

The best way to document a bug fix for knowledge sharing is to use a workflow that generates a self-improvement patch. This captures the diagnostic process and required patches for iterative team learning.

Can I apply an immediate patch instead of creating a full fix plan?

Yes, you can apply an immediate patch by choosing the fix now mode. This directly resolves the identified codebase bug while still enforcing mandatory logging and suggesting tests to prevent regressions.

Why do I need mandatory logging when patching codebase bugs?

Mandatory logging is required when patching codebase bugs to provide verifiable guardrails around the fix. It ensures traceability of the applied patches and supports the suggested tests to prevent future regressions.