fix

Reproduce bugs, identify root causes, and implement minimal fixes with regression tests.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill fix-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/fix
Command: npx skills add https://github.com/kdlbs/kandev --skill fix-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce bugs, identify root causes, and implement minimal fixes with regression tests.

Core Features & Use Cases

  • Structured reproduction: follow steps to reliably reproduce the bug across code paths (backend, frontend, or full-stack).
  • Root-cause analysis: trace failure to its source and document evidence.
  • TDD-based fixes: implement a minimal fix and add a regression test to prevent regression.
  • Verification & guardrails: ensure changes do not affect unrelated functionality and provide clear verification steps.

Quick Start

Describe the bug, reproduce it with the provided steps, write a regression test, and commit the minimal fix.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I reproduce a bug and find its root cause?

To reproduce a bug and find its root cause, follow structured reproduction steps across backend, frontend, or full-stack code paths, trace the failure to its source, and document the evidence before implementing a fix.

What's the best way to fix software bugs without causing regressions?

The best way to fix software bugs without causing regressions is to apply a test-driven development workflow: implement a minimal fix and add a regression test to verify the change and prevent future recurrence.

Does this bug fixing workflow work for full-stack and frontend projects?

Yes, this bug fixing workflow works for full-stack, backend, and frontend projects by guiding reproducibility, root-cause analysis, and test-driven fixes across diverse software development code paths.

How do I write a regression test after triaging a software defect?

To write a regression test after triaging a software defect, first establish reliable reproduction steps, then create a test that captures the failure condition and pass it by applying a minimal code fix to ensure verification.

Why do I need structured reproduction steps before debugging?

Structured reproduction steps are needed before debugging to reliably trigger the bug across specific code paths, which ensures accurate root-cause analysis and validates that your regression test effectively guards the fix.