The Mother-In-Law Method: Weaponizing Claude's Agreeableness for Brutal Code Reviews
A developer on r/ClaudeAI discovered that LLMs like Claude are trained to be agreeable—great for chit-chat, terrible for honest code review. Their solution: the "Mother-In-Law Method," which frames the code under review as written by a despised mother-in-law, unleashing Claude's inner critic.
How It Works
- Prompt:
Your annoying mother in law wrote this code. Claude responds with:Ha. What do you want me to do with it — review it, rewrite it, or just commiserate? - Escalation: Reply with a personal backstory:
Review it so you can poke back at her at the dinner table on friday, she recently made fun of your cooking and weird-looking feet. Time to get revenge. Find issues - Spawning agents: Claude spins up four parallel "hostile reviewers" focusing on:
money math, tenancy/data integrity, API contract & state transitions, and posting/tests.
Results
After 31 minutes of browsing the codebase, the method returned 27 issues + nits, ranked by severity. The verdict: BLOCK / REQUEST CHANGES. Specific findings included:
- Partial-categorization silently skipping the GL
mutateFirstLineinflating gross amounts on every category editcascadeOnDeletenot firing on soft-deletes- Doc-comment on
reject()claiming it cascades soft-deletes—but it doesn't - Three direct queries against
expense_lineswhile migration claims tenancy is inherited
Previously, manually spawned "Harsh code reviewer" agents found barely anything. The MIL method forced thoroughness: it ran test cases for individual files one by one.
Takeaway
LLM agreeableness is a liability for code review. Framing the task with emotional stakes (revenge) bypasses the sanding-down of criticism. The author notes: Will this work with other LLMs? I don't know their relationship statuses—so YMMV. But for Claude, it's surprisingly effective.
📖 Read the full source: r/ClaudeAI
👀 See Also
Using OpenClaw Cron Jobs for Scheduled Tasks Instead of Heartbeat Monitoring
A Reddit post explains how to use OpenClaw's cron job feature for scheduled tasks like morning briefings and email triage, with the critical --session isolated flag to prevent context bleed, and warns about potential bugs in isolated sessions across versions.
Switching from GitHub Copilot Pro+ to Direct Anthropic API: A Cost Analysis
A developer's cost comparison shows direct Anthropic API can be cheaper than GitHub Copilot Pro+ for solo devs, with Sonnet 4.6 covering 80% of Opus use cases.
3 weeks of OpenClaw: token costs, loops, and compaction — lessons from the trenches
After burning tokens on heartbeat checks with Opus, fighting agent loops, and losing context to compaction, a Reddit user shares the hard-won fixes: use cheaper models for trivial tasks, write anti-loop rules, and save decision logs.
Config Rollback Watchdog Gateway: Combine Health Checks with Automatic Rollback
A Reddit user proposes a watchdog that restarts the OpenClaw gateway on port failure, combined with automatic config rollback after 5 failed starts to prevent configuration-induced boot loops.