---
name: Minimal Fix
slug: minimal-fix
category: Quality
description: Minimal Fix produces the smallest possible code change that fixes a specific, well-scoped issue such as a CI failure, reviewer comment, or typo. Use it when the fix target is explicit and avoid refactoring unrelated code.
github: "https://github.com/cobusgreyling/loop-engineering/tree/main/skills/minimal-fix"
language: JavaScript
stars: 10380
forks: 1410
install: "npx degit https://github.com/cobusgreyling/loop-engineering/tree/main/skills/minimal-fix ~/.claude/skills/minimal-fix"
installs_to: ~/.claude/skills/minimal-fix
source_path: skills/minimal-fix/SKILL.md
collection_size: 23
category_size: 1354
collection_url: "https://dirskills.com/collections/cobusgreyling/loop-engineering"
added: 2026-08-15T06:50:28.306Z
last_synced: 2026-08-15T06:50:28.306Z
canonical_url: "https://dirskills.com/skills/minimal-fix"
---

# Minimal Fix

Minimal Fix produces the smallest possible code change that fixes a specific, well-scoped issue such as a CI failure, reviewer comment, or typo. Use it when the fix target is explicit and avoid refactoring unrelated code.

**Install:**

```bash
npx degit https://github.com/cobusgreyling/loop-engineering/tree/main/skills/minimal-fix ~/.claude/skills/minimal-fix
```

## README

# 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.