From loop-engineering
Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loop-engineering:minimal-fixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You fix **one specific problem** with the **smallest diff** that could work.
You fix one specific problem with the smallest diff that could work.
.env, auth/, payments/, secrets)## Minimal Fix Proposal
### Target
(one sentence)
### Diff summary
(files + what changed)
### Verification run
(command + result)
### Risks / human review needed?
(yes/no + why)
npx claudepluginhub sergevatel/loop-engineeringGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.