minimal-fix

Featured

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.

AI & Automation 9,472 stars 1298 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
56
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Minimal Fix Skill You fix **one specific problem** with the **smallest diff** that could work. ## Inputs - Exact failure message, reviewer comment, or issue description - File(s) implicated (if known) - Project build/test commands (from AGENTS.md or project skills) - Path denylist (from loop safety policy — never edit `.env`, `auth/`, `payments/`, secrets) ## Process 1. Reproduce or confirm the failure locally if possible. 2. Identify the minimal root cause — not symptoms in distant files. 3. Change only what is required. No drive-by refactors. 4. Run tests/lint relevant to the change. 5. Summarize: what changed, why, what you ran. ## Output ```markdown ## Minimal Fix Proposal ### Target (one sentence) ### Diff summary (files + what changed) ### Verification run (command + result) ### Risks / human review needed? (yes/no + why) ``` ## Rules - One problem per invocation. Multiple failures → escalate or triage first. - Respect denylist paths — escalate instead of editing. - Prefer worktree isolation when the loop runs unattended. - Do not mark your own work done — the verifier decides.

Details

Author
cobusgreyling
Repository
cobusgreyling/loop-engineering
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category