Launched this week
No Excuses
6 hooks that stop Claude Code from faking "done"
13 followers
6 hooks that stop Claude Code from faking "done"
13 followers
Claude Code's #1 problem: it says "β
Done!" but never ran the tests. CLAUDE.md rules get ignored β they're just suggestions. No Excuses is 6 Node.js hooks that ENFORCE: π finish-gate β blocks "done" until tests pass π task-gate β no stopping with unfinished steps β rule-guard β blocks rm -rf, force-push,env edits π read-guard β stops token waste π§ context-keeper β memory survives compaction π audit-guard β blocks secret leaks Works on Windows. Zero deps. 2-min install.
Payment Required
Launch Team / Built With
I built this while shipping my own SaaS (BillReach) almost entirely with Claude Code β after the tenth time "Done!" meant "tests failing."
CLAUDE.md rules didn't help (Claude ignores them), so I moved enforcement to hooks. An exit code can't be argued past.
finish-gate is my favorite: Claude tries to stop β it runs your tests β fail = blocked, sent back to fix. "Done" finally means done.
Happy to answer any questions about how the hooks work!
the rule-guard hook saved me from a force-push i almost did on main, install took about two minutes and it just worked. finally something that actually blocks me instead of just suggesting
honestly the finish-gate hook alone sold me, claude kept claiming tests passed when they obviously didn't. set this up in like three minutes and the rule-guard already saved me from a sketchy env file edit. solid stuff.
Love the rules-enforcing hooks, this feels like the missing guardrails for Claude Code. One thing I'd love to see added is a quick `npx no-excuses status` command (or similar) that shows which hooks fired and how often in the last session, so you can spot which rules you're tripping the most and tighten things up. Would make tuning the ruleset way easier than grepping logs.
The hooks sound like a lifesaver for keeping Claude honest, especially the finish-gate since lying about passing tests is exactly what wastes my afternoon. One thing that would help me a lot is a "dry-run mode" where the guards log what they would have blocked without actually stopping the work, so I can tune the rules for a new project without fighting the assistant mid-task.
The finish-gate idea is genuinely useful, especially the part about blocking "done" until tests actually pass. One thing that would make this a no-brainer for my team though is a dry-run mode where the hooks log what they would block without actually blocking, so we can test the guard rails safely before rolling them out to everyone without worrying about it getting in the way during evaluation or experimentation.