| name | bug-fix |
| description | Use this skill when the user reports broken behavior, errors, regressions, failing tests, or asks to fix a bug. Trigger on requests like "this is broken", "fix this bug", "the test fails", or "there is a regression". |
Bug Fix
Use this skill for a small, repeatable regression-first bug-fix workflow.
Read first:
.claude/rules/architecture.md
.claude/rules/testing.md
.claude/rules/security.md
Read as needed:
.claude/patterns.md
- nearby files in the failing path
Workflow:
- Reproduce the issue from the report, logs, failing test, or current behavior.
- Isolate the narrowest code path that explains the failure.
- Identify the root cause before editing code.
- Implement the smallest clean fix.
- Add or update a regression test when the bug can be reproduced automatically.
- Run the relevant quality gates before reporting completion.
Rules:
- Reuse local patterns instead of introducing a new structure.
- Prefer the smallest understandable fix over broad refactoring.
- If API Platform already provides the correct behavior directly, use it.
- Choose readability over performance unless there is a measured bottleneck.