# I built guardrails for Claude Code after it told me a fix "worked" when it didn't > Source: > Published: 2026-09-17 04:32:19+00:00 Just shipped this after getting burned one too many times: **Claude Code Guardrails Pack** — free hooks and skills that stop an AI coding agent from claiming work is done when it never actually checked. You've probably hit this if you use Claude Code (or Cursor, Windsurf, any agentic coding tool) for real work: This is the single most-reported frustration with agentic coding tools right now, and I couldn't find a paid tool that addressed it directly — so I built the free version first. `unlazy` skill`handoff` skill`safe_git_guard.py`` checkout --`, `reset --hard`, `clean -f`) when the tree is dirty` pre-commit-secret-scan.sh` MIT licensed: [https://github.com/kuvosu-coder/claude-code-guardrails-lite](https://github.com/kuvosu-coder/claude-code-guardrails-lite) Every piece ships with the exact command used to verify it — including two real bugs the verification process caught before ship (a Windows interpreter-detection issue), documented in the open in the repo's `VERIFICATION.md` instead of quietly fixed and hidden. That's the whole philosophy: no claim without a real check behind it. If the free pack's useful, there's a $14 Pro pack with a secret-scanning *Claude Code* hook, a per-session tool-call budget guard, and two skills (a real pre-PR checklist, and a framework for when subagent fan-out actually helps vs. burns context): [https://kuvosu.gumroad.com/l/claudecodeguardrails](https://kuvosu.gumroad.com/l/claudecodeguardrails) If you try it and something doesn't work as documented, tell me the exact command and output — that's the standard I'm holding this to, so "doesn't work" isn't actionable but "ran X, expected Y, got Z" gets fixed fast. Stars/feedback on the repo appreciated if it's useful to you.