ceratops-code-consistency-audit

To check repository coherence after a large branch merge, audit the codebase to surface contradictions between code, docs, tests, configurations, and examples. This validates that merged changes align with declared sources of truth and reports actionable fixes.

Documentation drift detection identifies contradictions between implementation and documentation, configs, or examples. You need it during release-readiness checks or post-merge validation to ensure technical docs accurately reflect merged code changes.

To find merged-only edge cases and stale references before a release, run a cross-cutting consistency audit across READMEs, configs, tests, manifests, and automation. This surfaces issues introduced by parallel agent work or refactors.

Yes, a consistency audit supports release-readiness checks by validating coherence across multiple configuration files, manifests, and tests. It enforces declared sources of truth and reports concrete inconsistencies with actionable fixes.

The best way to validate code and test consistency after parallel agent work is to run a repository coherence audit. It detects drift between implementation, tests, and examples, surfacing contradictions introduced by parallel threads.

This consistency audit focuses on cross-file contradictions rather than style review. It targets documentation drift, merged-only edge cases, and contradictions between code, docs, tests, and configurations after major refactors.