Mending

Repair a single broken artifact - a config, a file, a build, a migration - without redesigning it.

What This Skill Does

Mending is surgical repair of a known-working artifact that has a specific, identifiable break. It is NOT:

Triage/diagnosis: If the problem is "API is throwing 500s, figure out why" — that's investigation, not mending. Mending requires the break to already be identified.
Formatting/cleanup: If the data is correct but looks messy (sort keys, normalize indentation) — that's formatting, not repair.
State reset: If a flag is stuck or an alert needs clearing — that's an operational toggle, not a file repair.
Refactoring/redesign: If the system is "fundamentally flawed" and needs redesign — that's rebuilding, not mending.
Comprehensive cleanup: If there are "years of orphaned records" across tables — that's a data integrity project, not a surgical fix. In this grimoire, Mending is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Mending (spell).

Trigger this spell when the request contains:
A specific file or artifact named (e.g., .gitignore, docker-compose.yml, Makefile, package.json, migration script, manifest)
A localized break: syntax error, typo, missing character, wrong reference, indentation issue, unclosed bracket, trailing comma, misspelled key
Evidence the artifact was working before ("broke yesterday", "was fine last week", "worked before the merge")
Language like: "just fix", "repair", "fix the typo", "missing semicolon", "broken reference", "indentation error", "without changing"