Tools
Tools: Breaking: I shipped cc-audit as a GitHub Action. Now your CLAUDE.md gets linted on every PR.
The workflow
What you get
Auto-install the baseline
End-to-end demo
Why bother
Install time Quick follow-up to my earlier post about scanning 492 public CLAUDE.md files. Takeaway from that scan: median compliance with the 12-rule baseline was 3/12. The top-missed rules were rules 9, 10, 12, and 1 — the behavior-file equivalent of skipping unit tests. The fix is easy: run a linter. The harder part is remembering to run it. So I packaged cc-audit as a GitHub Action. Drop three lines into your repo's workflow, and every push that touches CLAUDE.md or AGENTS.md gets an automatic report in the run summary — plus a hard fail if someone ever pastes a real API key into the behavior file. Every matching push/PR runs cc-audit against the file. The run summary shows: The step fails with a loud ::error:: annotation if any leaked-secret pattern is detected — OpenAI keys, Anthropic keys, GitHub PATs, AWS access keys, Stripe live keys, postgres URLs with credentials. Placeholder-aware, so <YOUR_KEY> and sk-example-... don't trigger false positives. By default it doesn't fail the build on mere rule-coverage warnings, because a 7/12 file isn't "broken" — it's just not thorough. You can flip that with: There's also a companion action for the claude-code-pro-pack itself. If your repo doesn't have a CLAUDE.md / AGENTS.md yet, this installs the 12-rule baseline in one step: It's polite — skips files that already exist unless you pass overwrite: true. I shipped a demo repo that uses both actions: → github.com/sisyphusse1-ops/ccpp-demo Check the Actions tab — you'll see real runs installing the pack, then linting it. The install workflow is workflow_dispatch so you can fork the repo, trigger the install on your fork, and watch the same thing happen on your own files. Three reasons I wrote this and why you might want to run it: Workflow file: 3 lines.
CI overhead per run: 20-30 seconds on ubuntu-latest (no Docker image pull, just checkout + Python stdlib).Token cost: zero.
Cost to break your build: zero if no secrets leaked. If this saves you a merge review, or catches a leaked key, let me know. That's the use case I optimized for. Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse
