Add config-drift-checker to Code Quality Testing - #454
Open
jameskomo wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding my project, config-drift-checker: CI for a repo's Claude Code setup. It turns CLAUDE.md, skills and hooks into eval cases, re-runs them on every Claude Code release and on PRs that touch the config, and diffs against a pinned baseline with noise-aware verdicts so judge flakiness doesn't cause false alarms.
To show it catches real breakage there is a published self-sabotage demo: a deliberately broken skill trigger takes the suite from 1.00 to 0.36 with the tripwire case at 0.00 (https://jameskomo.github.io/config-drift-checker/example-break/report.html).
Placed under Code Quality Testing in alphabetical order. Happy to adjust format or section if you prefer.