Claude Code hooks and skills that mechanically block edits to files the agent hasn't read this session. Not a checklist but a working system for features and bugs.
Description: Claude Code doesn't fail loudly. It fails by being confidently, plausibly wrong — stating something about your code it never actually checked, assuming a shared type's shape instead of reading it, editing a centralized config without knowing what else depends on it. A green test suite doesn't catch this. A code review doesn't always catch it either, especially when you're the only reviewer. This kit is the discipline that does. It isn't a set of prompts to remember or a checklist to follow through willpower — it's two hooks that mechanically block an edit to a file Claude hasn't read this session, and nine skills that run the discipline instead of describing it: one that scopes a new feature or migration from a few keywords automatically, one that enumerates every real consumer of a file before you touch it, one that reads your own diff like a stranger would before you call it done. All of it was tested end-to-end against real Claude Code payloads before it shipped — not just described — including a TypeScript example that actually compiles under --strict and an installer verified against four real scenarios, including a project that already has its own hooks. Behind the mechanics is a twelve-stage methodology and six real failure patterns, generalized from two years of exactly this kind of work, so every rule comes with the reasoning for why it exists — not just the instruction to follow it. What you get: Two Python hooks enforcing read-before-edit, zero dependencies, tested against six real allow/block scenarios Nine Claude Code skills — six auto-invoke on their own when the situation fits, no command to remember METHODOLOGY.md — twelve stages from scope to handoff, including the closing-the-loop step most kits like this skip: verifying your own last session's handoff before trusting it LESSONS.md — six real failure-pattern case studies, each tied to the specific rule or skill that catches it faster A one-command installer, tested against four scenarios including a project with pre-existing hooks — never overwrites what you've already built A plain-text version for ChatGPT, Cursor, or any tool without hooks or skills Private GitHub repo access after purchase (invited within a week or two if GitHub User is provided to my email) — updates land there as the system improves, not a zip you download once and it goes stale An invite to a Discord server that's just getting started for buyers — comparing notes on what your own sessions catch, and a say in what gets built next, not an existing community to browse
Get it → briandev5.gumroad.com