unikit-fix

Automate end-to-end bug-fix workflows in UniKit AI projects.

16|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unikit-fix
Source: https://github.com/NintendaDev/unikit-ai/tree/main/skills/unikit-fix
Command: npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Fix workflow automates the end-to-end process of diagnosing, planning, implementing, and validating code fixes within UniKit AI, reducing manual overhead for developers.

Core Features & Use Cases

  • Plan-driven fixes: Create, store, and follow a .unikit/FIX_PLAN.md to guide multi-file changes.
  • Patches & patches-tracking: Generate patches under .unikit/patches and associate patches with problem context for future reuse.
  • Safe execution: Use Read/Edit/Write tools and delegated agents for complex changes while enforcing project rules from the bootstrap context.
  • Verification workflow: Validate changes with compilation and test runs via the engine toolchain and respect architecture constraints.

Quick Start

Describe the bug succinctly and send /unikit-fix <description> to start an end-to-end fix workflow.

Frequently Asked Questions about unikit-fix

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

FAQPage Schema
How do I automate bug fixes across multiple files in my development workflow?

Automated bug fixes are orchestrated through a guided workflow that diagnoses issues, creates a plan in FIX_PLAN.md, applies patches, and verifies compilation. This enforces architecture constraints while reducing manual overhead for multi-file changes.

Can I fix compilation errors and missing references without manually writing patches?

Compilation errors and missing references are patched automatically under the .unikit/patches directory. The workflow uses Read, Edit, and Write tools to apply changes directly, tracking the problem context for future patch reuse.

Does the bug fix workflow require a plan before applying code patches?

A plan is enforced via .unikit/FIX_PLAN.md to guide multi-file changes, but you can choose between plan-first or immediate-fix modes. This ensures safe execution while accommodating both complex and straightforward bug fixes.

What is the best way to ensure runtime bug patches respect existing architecture constraints?

Architecture constraints are respected by reading rules from .unikit/ARCHITECTURE.md during the fix workflow. The process validates changes against these constraints and runs verification workflows using the engine toolchain.

Why use a guided workflow for patching runtime bugs instead of applying direct edits?

Guided workflows ensure safe execution by delegating complex edits to agents and tracking patches with problem context. This structured approach prevents regression by validating fixes with compilation and test runs before completion.