fix

Write and validate a targeted code fix for a confirmed bug.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ahliweb/sikesra --skill fix-ahliweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/ahliweb/sikesra/tree/main/awcmsmicro-dev/.flue/skills/fix
Command: npx skills add https://github.com/ahliweb/sikesra --skill fix-ahliweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a confirmed bug report into a safe, verified code fix without drifting into unrelated changes or leaving the repository in an unvalidated state.

Core Features & Use Cases

  • Targeted Bug Repair: Focuses on the diagnosed root cause and keeps the edit scope as small as possible.
  • Regression Validation: Reproduces the failure where feasible, then proves the fix with tests, typechecking, linting, and formatting.
  • Repository Discipline: Stages the finished work for the orchestrator while avoiding commits, pushes, and other prohibited Git operations.
  • Use Case: A broken API route, query, handler, or UI behavior is reported with high confidence, and this Skill is used to implement the fix and verify it end to end.

Quick Start

Use the fix skill to repair the confirmed bug, run the appropriate regression checks, and stage only the files needed for the validated change.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I implement a code fix for a confirmed bug without introducing unrelated changes?

To implement a code fix without drift, target the diagnosed root cause and keep the edit scope as small as possible. This approach ensures your bug repair remains focused solely on the isolated regression.

What's the best way to validate a bug fix before staging changes?

The best way to validate a bug fix is to reproduce the failure, then prove the fix with regression testing, unit tests, integration checks, typechecking, linting, and formatting to ensure repository stability.

Does this bug fix workflow support EmDash plugin and application repositories?

Yes, you can use this bug fix process for EmDash plugin and application repositories where reproduction, unit, integration, or browser checks are used to isolate regressions and verify the targeted code changes.

Why should I avoid commits and pushes when applying a code fix to my repository?

You should avoid commits and pushes because this bug fix workflow maintains repository discipline by staging finished work for the orchestrator while avoiding prohibited Git operations during the regression validation process.

What steps are needed to turn a confirmed bug report into a verified code fix?

To turn a bug report into a verified fix, apply a targeted code repair to the root cause, run package test execution and typechecking, apply linting and formatting, and stage the validated files following repository conventions.