Paste any GitHub repo. We'll show you exactly where Copilot, Cursor, and Claude configs have drifted from your actual CI pipeline.
Search or paste any public GitHub URL above. We clone it in a sandbox.
CI pipelines, CLAUDE.md, .cursorrules, AGENTS.md, Copilot instructions — all cross-referenced.
Stale configs, rules that reference tools you don't use, CI gates missing from AI instructions.
You wrote rules for Copilot or Claude. Then your CI pipeline changed — new linters, updated commands, removed tools. Now your AI tools follow outdated instructions and produce code that fails in CI. That gap is config drift.
Your CLAUDE.md was last updated 3 months ago, but package.json scripts changed since. The AI runs npm test when you switched to vitest run.
Your .cursorrules says "always run eslint" — but you migrated to Biome and removed ESLint. The AI runs a linter that doesn't exist.
You have GitHub Actions and CLAUDE.md but no .cursorrules. Cursor users get zero guidance from your repo.
Your CI runs prettier --check but none of your AI config files mention formatting. AI-generated PRs fail the formatter every time.
Cloning and auditing...
This can take 5-15 seconds for large repos
Fix all drift in 30 seconds:
Click to copy. Or set up continuous drift prevention with crag hook install