vivary
CLAUDE.md1 starsChanged 48 days agoMITView on GitHub
Read AGENTS.md and its governing engineering policy. This file adds only Claude Code behavior. Older workflow preferences cannot restore heavier verification defaults. Before a merge that needs approval, prepare the concrete change, relevant verification, remaining risks, and the requested merge action. Use plan mode when it helps make a substantial design reviewable. Do not require a separate plan approval before routine authorized implementation, tests, or retries. Specific merge approval still applies. If scope changes materially, explain the change before the…
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- entire-searchSkill
- loopsSkill
- maintain-hlddSkill
- entire-searchSkill
- entireSkill
- loopsSkill
- maintain-hlddSkill
The file
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read AGENTS.md and its governing engineering policy.
- Distinctive: line 9
Before a merge that needs approval, prepare the concrete change, relevant verification, remaining risks, and the requested merge action.
- Distinctive: line 18
Use planning subagents, loops, and additional reviewers when they justify their cost for the actual work.
- Distinctive: line 25
Keep this file lean and put durable product decisions in their existing owner.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code instructions
Read AGENTS.md and its governing engineering policy. This file adds only Claude Code behavior. Older workflow preferences cannot restore heavier verification defaults.
Merge alignment
Before a merge that needs approval, prepare the concrete change, relevant verification, remaining risks, and the requested merge action. Use plan mode when it helps make a substantial design reviewable. Do not require a separate plan approval before routine authorized implementation, tests, or retries. Specific merge approval still applies. If scope changes materially, explain the change before the gated action.
Optional tools
Use planning subagents, loops, and additional reviewers when they justify their cost for the actual work. They are not default phases. Preserve stop conditions for expensive or dangerous jobs and all external-action gates.
The skills index and command reference route to optional tools. The original CLI reference owns package release status. Keep this file lean and put durable product decisions in their existing owner.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.