narrow-patch-authoring

What problem does it solve?

When fixing production bugs, developers often add unnecessary refactoring, tech debt cleanup, or address symptoms instead of root causes, leading to larger, riskier changes that introduce new issues and slow down code reviews.

Core Features & Use Cases

• Root Cause-Only Fixes: Enforces changes that exclusively address the identified root cause from forensic evidence, with no unrelated modifications.
• Invariant Preservation Checks: Includes a self-review checklist to ensure existing system behavior, position entry/exit, and dashboard metrics remain intact after the patch.
• Evidence-Backed Commits: Requires commit messages that cite concrete forensic evidence (logs, code paths, state) for full traceability.
• Use Case: For a developer debugging a timeout bug in a crypto trading bot's paper trade executor, use this skill to create a 2-line patch that fixes the wrong variable reference, without cleaning up unused functions or renaming variables for clarity.

Quick Start

Use the narrow-patch-authoring skill to create a minimal patch that fixes the root cause of the timeout bug identified in the latest forensic report, without adding any unrelated changes or refactoring.