From bake-claude-md-files
Converts CLAUDE.md rules into automated checks using tools like ESLint, PHPStan, Pint, Ruff, Prettier, and CI; verifies passes and removes rules to free agent context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bake-claude-md-files:bake-claude-md-filesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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).
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:
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.
npx claudepluginhub publicala/bake-claude-md-files-skill --plugin bake-claude-md-filesOptimizes CLAUDE.md hierarchies, .claude/rules, ecosystem files, and docs/ folders per Anthropic best practices. Detects redundancies, conflicts, and suggests improvements.
Provides best practices for creating, updating, and auditing CLAUDE.md files including constraints, commands, architecture overviews, and bloat reduction for projects.
Generates project-specific CLAUDE.md rules by detecting stack from package.json, Cargo.toml, pyproject.toml, go.mod, git log, and user-selecting categories like response format, library preference, code review stance. Use for new projects, repo onboarding, or establishing conventions.