evolution-loop

name	evolution-loop
description	Run a bounded repository improvement loop using explicit fitness criteria, small reversible mutations, validation evidence, and human approval gates.

Evolution Loop

Use this skill when the user wants FullSelfDriving to improve a repository, not just audit it.

Loop

1. Define explicit fitness criteria.
2. Inspect existing repo instructions and validation commands.
3. Generate small candidate changes.
4. Validate candidates with the narrowest meaningful checks.
5. Score by evidence.
6. Keep the best patch and discard weak candidates.
7. Hand off with commands run, artifacts, risks, and next candidate improvements.

Fitness Criteria

Common criteria:

• tests pass
• lint/typecheck pass
• coverage improves without meaningless tests
• app health check passes
• screenshot or trace confirms UI behavior
• complexity decreases
• debug evidence becomes easier to collect
• isolation improves

Guardrails

• Do not delete, skip, or weaken tests to improve scores.
• Do not hide errors.
• Do not add mocks outside legitimate test seams.
• Do not run unbounded loops.
• Do not make destructive changes without explicit approval.
• Prefer one well-validated improvement over many speculative edits.