Skill323 repo starsupdated today

minimal-fix

The minimal-fix skill diagnoses a single failure or issue and applies the smallest possible code change to resolve it, respecting security denylists and avoiding unnecessary refactoring. Use this when a specific error message, test failure, or reviewer comment pinpoints one problem that needs a targeted fix with minimal diff footprint.

View source Repository: loop-engineering

Install in Claude Code

Copy

git clone --depth 1 https://github.com/cobusgreyling/loop-engineering /tmp/minimal-fix && cp -r /tmp/minimal-fix/skills/minimal-fix ~/.claude/skills/minimal-fix

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

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