Mending
Repair a single broken artifact - a config, a file, a build, a migration - without redesigning it.
Overview
Mending is interpreted here as a metaphorical spell with a shipping-now execution model.
Canonical source: Mending (spell)
Provider target: OpenClaw
When To Use
- 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"
Workflow
- Confirm the break is specific and localized — name the exact file, the exact error, and what "working" looked like before.
- Apply the minimal change that restores the original behavior — fix the typo, add the missing character, correct the reference, move the misplaced directive. Do not improve, modernize, or restructure.
- Show a before/after diff so the repair is auditable and reversible.
- If the break reveals a deeper structural problem (e.g., the same typo appears in 12 files, or the config format is fundamentally unsound), report it — do not paper over it with repeated patches.
Deliverables
- The repaired artifact in working condition.
- A before-and-after diff showing exactly what changed.
- A note if the break suggests a deeper structural issue.
Guardrails
- Fix the break. Do not redesign. Do not "take the opportunity to clean up."
- If the damage is too extensive for a targeted repair, say so and recommend a larger intervention.
- Preserve the artifact's original design, style, and structure.
- Do not use for: "Diagnose why production is broken" → investigation spell
- Do not use for: "Clean up formatting on this file" → formatting spell
- Do not use for: "Reset this stuck flag/alert" → operational spell
- Do not use for: "Redesign this module from scratch" → refactoring spell
- Do not use for: "Clean up data integrity across all tables" → data project spell
Default Invocation
Use $mending to fix this broken artifact with the smallest repair that restores it to working condition.
1---2name: mending3description: 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.4---56# Mending78Repair a single broken artifact - a config, a file, a build, a migration - without redesigning it.910## Overview1112Mending is interpreted here as a metaphorical spell with a shipping-now execution model.1314Canonical source: Mending (spell)1516Provider target: OpenClaw1718## When To Use1920- Trigger this spell when the request contains:21- A specific file or artifact named (e.g., .gitignore, docker-compose.yml, Makefile, package.json, migration script, manifest)22- A localized break: syntax error, typo, missing character, wrong reference, indentation issue, unclosed bracket, trailing comma, misspelled key23- Evidence the artifact was working before ("broke yesterday", "was fine last week", "worked before the merge")24- Language like: "just fix", "repair", "fix the typo", "missing semicolon", "broken reference", "indentation error", "without changing"2526## Workflow27281. Confirm the break is specific and localized — name the exact file, the exact error, and what "working" looked like before.292. Apply the minimal change that restores the original behavior — fix the typo, add the missing character, correct the reference, move the misplaced directive. Do not improve, modernize, or restructure.303. Show a before/after diff so the repair is auditable and reversible.314. If the break reveals a deeper structural problem (e.g., the same typo appears in 12 files, or the config format is fundamentally unsound), report it — do not paper over it with repeated patches.3233## Deliverables3435- The repaired artifact in working condition.36- A before-and-after diff showing exactly what changed.37- A note if the break suggests a deeper structural issue.3839## Guardrails4041- Fix the break. Do not redesign. Do not "take the opportunity to clean up."42- If the damage is too extensive for a targeted repair, say so and recommend a larger intervention.43- Preserve the artifact's original design, style, and structure.44- Do not use for: "Diagnose why production is broken" → investigation spell45- Do not use for: "Clean up formatting on this file" → formatting spell46- Do not use for: "Reset this stuck flag/alert" → operational spell47- Do not use for: "Redesign this module from scratch" → refactoring spell48- Do not use for: "Clean up data integrity across all tables" → data project spell4950## Default Invocation5152Use $mending to fix this broken artifact with the smallest repair that restores it to working condition.53
Hmbown