---
title: "Comment by Mihai_LeanZero on \"A Working CLAUDE.md/AGENTS.md Template You Can Copy Today\" | Hashnode"
description: "The do-not-touch section is the part I'd lean on hardest. We keep something similar across our own repos and the plain list alone doesn't hold up on its own --"
url: "https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0bf9469f008697a5c2e45"
---

[Discussion](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906)

Comment [A Working CLAUDE.md/AGENTS.md Template You Can Copy Today](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 21](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0bf9469f008697a5c2e45)

The do-not-touch section is the part I'd lean on hardest. We keep something similar across our own repos and the plain list alone doesn't hold up on its own -- an agent working under task pressure will still edit a frozen path if nothing but a comment is stopping it. What's actually worked for us is a pre-commit check that rejects any diff touching those paths unless a human explicitly overrides it, so the rule gets enforced rather than just documented. The review\_cadence field in the header is a nice idea too, but I'd want something checking it -- a stale last\_updated sitting there for six months doesn't page anyone on its own, it just quietly stops being true.

[Dhrutika Rathod](https://hashnode.com/@dhrutikarathod)

[Sep 21](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0bf9469f008697a5c2e45#reply-6ab0c1d8c7c566a49754d58c)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero "Mihai_LeanZero") - This is a really good point. A do-not-touch list is a documentation-layer fix for what's ultimately an enforcement-layer problem — under task pressure, "explicitly told not to" and "structurally prevented from" are very different guarantees, and I was implicitly leaning on the former. The pre-commit check with an explicit human override is the right shape for this. It also fixes a subtler issue: a written rule can be technically correct but still get "worked around" by an agent that convinces itself an edit is fine, whereas a hard gate doesn't care about the justification. Same logic applies to your review\_cadence point, and I think it's the sharper of the two - a metadata field that nobody's watching is really just a comment with extra steps. A CI check that flags any file where last\_updated is older than the stated cadence (and fails the build, or at least nags loud enough to be annoying) turns it from a norm into something that actually gets caught. Do you enforce the cadence check in CI, or is it more of a periodic manual audit on your end? Curious how granular you've gone with it — per-file, per-directory, or one blanket rule for the whole context file.

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 23](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0bf9469f008697a5c2e45#reply-6ab44cda024cfe9ced345a1d)

Right now it's closer to a manual audit than CI-enforced. I read through the file when something in that area breaks or when I'm touching it for other reasons, not on a fixed schedule, so no check currently flags a stale last\_updated on its own. If I built one, I'd make it per-directory rather than per-file or one blanket rule for the whole thing, since the actual failure mode is a whole area, an API surface, a workflow, drifting together, not a single line going stale in isolation. A single cadence for the entire file would end up either flagging stuff that's still fine or missing the part that's actually gone stale.
