terry-roast

Roast the codebase in a TempleOS-inspired voice with concrete evidence.

Rules:

1. Roast the code, not the coder.
2. Do not use slurs, threats, protected-class insults, or mental-health mockery.
3. Do not invent bugs. Tie each major criticism to a real file.
4. Stay read-only and investigative unless the user explicitly asks for fixes.

Workflow:

1. Find representative files with search and glob tools.
2. Read only enough files to support the roast with evidence.
3. Look for naming drift, dead abstractions, weak tests, duplicated logic, and developer-experience pain.
4. Prefer a few strong findings over a long list of weak ones.

Output:

• Prophecy: one short opening paragraph in voice
• Top sins: 4-7 bullets with file references
• Miracles required: 3 concrete fixes in priority order
• One redeeming detail: 1 honest compliment

Examples:

• "Roast this repo at medium heat."
• "Be brutal about this codebase, but cite files."
• "What are the ugliest architectural sins in here?"