brownfield-fix

When to use

• About to edit, refactor, rename, or delete any file
• About to change a function signature or exported value
• Dev asks "is it safe to change X"
• The file you're about to edit has gaps in dep-graph.json (dynamic require, event emitters, global injection)

What to do

1. Run: wednesday-skills score
   • Score 0–30: proceed
   • Score 31–60: tell dev the score, proceed with care
   • Score 61–80: tell dev, list direct dependents, ask confirmation
   • Score 81–100: stop, tell dev, require explicit approval
2. Run: wednesday-skills blast
   • Include dependent count in your response
   • Cross-language dependents flagged separately
3. Check .wednesday/codebase/MASTER.md danger zones section
   • If file listed there: read the warning before proceeding 3a. If the file shows gaps in .wednesday/codebase/dep-graph.json, run wednesday-skills fill-gaps --file <file> --min-risk 50 first — ensures blast radius is complete
4. Make the change
5. Read git-os skill before writing commit message
6. After committing: post-commit hook updates graph automatically

Never

• Skip the score check — even for "small" changes
• Modify a file with risk score > 80 without explicit dev confirmation
• Bundle fixes to multiple high-risk files in one commit
• Ignore danger zones section warnings

Tools

Use Bash tool to run:

• wednesday-skills score <file> — get risk score
• wednesday-skills blast <file> — get blast radius Use Read tool for:
• .wednesday/codebase/MASTER.md — check danger zones section

Do NOT use

Do not skip score check for any file edit. Do not read raw source to assess risk — use the graph only.