Menu

Post image 1
Post image 2
1 / 2
0

I shipped cc-audit as a GitHub Action. Now your CLAUDE.md gets linted on every PR.

DEV Community·sisyphusse1-ops·24 days ago
#gNN6jfO6
#github#ai#devops#actions#claude#audit
Reading 0:00
15s threshold

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. The workflow # .github/workflows/cc-audit.yml name : cc-audit on : pull_request : paths : [ ' CLAUDE.md' , ' AGENTS.md' ] push : paths : [ ' CLAUDE.md' , ' AGENTS.md' ] jobs : audit : runs-on : ubuntu-latest steps : - uses : actions/checkout@v4 - uses : sisyphusse1-ops/cc-audit@v1 Enter fullscreen mode Exit fullscreen mode That's it. What you get Every matching push/PR runs cc-audit against the file.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More