Developer builds CI tool to detect when Claude Code silently stops following your rules
A developer discovered that their 400-line Claude Code configuration had no automated tests, meaning model updates could silently break custom behaviors without any alerts. To address this, they built an open-source tool called config-drift-checker, which converts CLAUDE.md files, skills, and hooks into eval test cases that run on every Claude Code release or configuration change. While testing the tool, the developer intentionally sabotaged their own setup by altering a skill's trigger description, which caused the suite score to collapse from 1.00 to 0.36 and one key test to score zero across all runs. The tool uses a three-run-per-case method with history-based noise bands to distinguish genuine rule failures from random model variability, escalating to a red alert only when failures persist across consecutive runs. The tool runs as a GitHub Action and is free to use with a Claude Pro or Max subscription, with the source code available on GitHub.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in