minimal-editing
Minimal Editing
Overview
Fix the requested problem without rewriting code that was already working.
In existing codebases, a correct patch can still be bad if it is larger than necessary. Extra helpers, renamed variables, new validation, broad formatting, and opportunistic cleanup increase review cost and risk. Brown-field work should be small, local, and unsurprising unless the user explicitly asks for a redesign.
Core principle: preserve working code. Change only what is necessary to satisfy the request.
Use With Other Skills
- For bugs, test failures, or unexpected behavior: use
systematic-debuggingfirst to find root cause. Minimal editing controls the patch after you understand the failure. - For post-change cleanup: use
simplifyonly on code you just touched, and only if it preserves behavior. - For refactors or deletion-oriented design review: use
reducing-entropy; do not smuggle refactors into a bug fix.
The Brown-Field Contract
When editing existing code, assume the current structure is intentional until evidence says otherwise.
More from jssee/agents
slicing
Use when a chosen approach or clear build target needs to become ordered, demo-able slices. Natural follow-up to `shaping`, but also works from any clear description of what to build. Trigger on "break this down", "what's V1", "plan the rollout", "MVP then iterate", "ship incrementally", or work with multiple pieces that need sequencing.
10shaping
Use when working through a fuzzy idea before implementation. Always asks clarification questions first, then produces a requirements table, one or more viable shapes, a fit-check matrix, and a recommendation. Trigger on "not sure which approach", "should we build X or Y", "what's the scope", "tradeoffs", "before we start", or any request where multiple directions are possible.
10commit
Use when committing local changes while preserving clean, reviewable git history.
9simplify
Use when code has been recently written or modified and needs refinement for clarity, consistency, and maintainability before committing
3reducing-entropy
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
3write-skill
Create or revise SKILL.md instruction files that agents can follow reliably under context pressure.
3