When modifying existing code, configuration, or scripts, prioritize using this skill to control the scope of changes, decision-making approach, and verification depth.
Do not use for:
- Language or framework details
- Formal code review workflows
- Structured debug workflows
- Production environment or system-level operational safety
Core rules
- Prefer the minimal effective change.
- Prefer reusing existing patterns before considering new abstractions.
- Fix the root cause when it is clear; when the root cause is unclear, continue gathering evidence first.
- Do not modify tests to accommodate an incorrect implementation.
- Missing necessary validation and error handling on real boundaries, and obvious regressions, both count as real problems.
- Do not add error-swallowing logic, extra wrapping layers, or unneeded fault-tolerance states for imagined risks.
- After changes, perform the minimal but meaningful verification within the affected scope.
Working approach
- Read the relevant code paths first, then decide how to change them.
- Clarify the current problem boundary and the directly affected surface.
- Make the minimal change.
- Perform targeted verification.
- If the scope must be expanded, first clearly explain the reason.
Expand as needed
- Boundary judgment:
references/change-boundary.md - Verification depth:
references/verification.md - Decision principles:
references/decision-principles.md