bugfix-local

Reproduce, diagnose, and fix bugs locally with root-cause analysis and regression verification.

17|1|Updated Dec 29, 2019
One-click install
npx skills add https://github.com/LumaKernel/dotfiles --skill bugfix-local-lumakernel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix-local
Source: https://github.com/LumaKernel/dotfiles/tree/main/common/claude/skills/luma-web-bugfix
Command: npx skills add https://github.com/LumaKernel/dotfiles --skill bugfix-local-lumakernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing a bug is only half the job—without understanding why it slipped through, the same class of bug returns. This Skill guides a disciplined local bugfix workflow: reproduce the bug, identify the cause, apply a minimal fix, verify with type checks, lint, and tests, then perform root-cause analysis and implement structural prevention measures. ## Core Features & Use Cases - Guided Reproduction: Chooses the right reproduction method per bug type—failing tests, type checks, lint, dev server, or Storybook—and records the reproduction steps before fixing. - Minimal, Convention-Aware Fixes: Applies the smallest possible change while respecting project coding standards from CLAUDE.md and project configuration. - Root-Cause Analysis & Prevention: Uses git blame and git log to trace when the bug was introduced, then strengthens types, lint rules, compiler flags, tests, or architecture to prevent recurrence. - Use Case: A user reports a runtime error in a React component. The Skill reproduces it via Storybook, traces the cause through recent commits, fixes it, adds an exhaustive type check and a regression test, and reports the root cause with prevention measures. ## Quick Start Ask the AI to reproduce and fix the bug where submitting the form throws a type error, then verify with tests and explain the root cause.

Frequently Asked Questions about bugfix-local

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

FAQPage Schema
How do I reproduce and fix a bug locally before committing?▼

First check git status for uncommitted changes, then reproduce the bug using the appropriate method: a failing test, type check, lint command, dev server, or Storybook. Record the reproduction steps, apply a minimal fix, and verify with type checks, lint, and the full test suite.

How to find the root cause of a bug using git history?▼

Use git blame and git log to identify when and in which commit the bug was introduced. Review the commit diff to understand what should have been done differently and why review or tests missed it.

What verification steps should run after fixing a bug?▼

Run type checking, lint, and tests in that order—targeted test files first, then the full suite. If any step fails, revisit the fix. The bug is done only when it no longer reproduces and all existing tests pass.

How can I prevent the same type of bug from recurring?▼

Strengthen the mechanisms that failed to catch it: add stricter type constraints or branded types, enable exhaustive checks for unions and switch statements, add or tighten lint rules, and create test patterns covering the bug class. Document lessons in design docs or CLAUDE.md.

Does this workflow commit the fix automatically?▼

No. The fix is reported with cause, changed files and line numbers, root cause, and prevention measures, but committing always requires explicit user confirmation first.