| name | bake-claude-md-files |
| description | Converts CLAUDE.md rules into automated checks (eslint, phpstan, pint, CI, etc.), removes the automated rules from CLAUDE.md, and verifies everything passes. Frees up agent context by replacing prose with tooling.
|
| user-invocable | true |
| disable-model-invocation | true |
Read all CLAUDE.md files in the project, along with the existing tool configurations (eslint, phpstan, pint, package.json scripts, lefthook, git hooks, GitLab CI or GitHub Actions and everything else relevant).
Identify rules in the CLAUDE.md files that can be turned into automated checks. Every rule we can remove is context freed up for the agent.
Before modifying any CLAUDE.md file, present a summary of:
- Which rules will be automated (and by which tool)
- Which rules will be kept (and why - e.g. requires human judgment, context-dependent)
Only proceed after the user approves. Then implement the automated checks, verify everything passes, and only remove a rule from CLAUDE.md after its corresponding check passes.
Implementation priority
- Discover existing tooling first - inventory linters, test frameworks, static analyzers, CI pipelines, and git hooks before implementing anything
- Use native capabilities - express checks through tools already in the project:
- Linter/formatter rules (ESLint, Biome, Prettier, Pint, Ruff, gofmt)
- Static analysis (TypeScript strict, PHPStan, mypy, Rector)
- Architecture tests (Pest arch, ArchUnit, dependency-cruiser)
- Git hooks (Lefthook, Husky, pre-commit)
- CI pipeline steps
- Custom scripts only as last resort - only when no existing tool can express the check
- Wire into existing runners - new checks must run via existing test/lint commands, not new entrypoints
