enterprise-review

Cross-venture codebase drift detection works by parsing package.json, tsconfig.json, and CI workflows across local venture repositories to identify dependency, configuration, and tooling inconsistencies, summarizing them into a consolidated drift report.

You can run a targeted codebase consistency audit for a specific subset of ventures by applying the --venture codes flag, focusing the drift detection and reporting solely on the selected repositories instead of all available ventures.

Yes, auditing cross-venture codebase drift requires a crane-console workspace and access to local ~/dev/{code}-console repositories to parse configurations like package.json, tsconfig.json, and CI workflows for tooling inconsistencies.

The best way to report on codebase structure and tooling inconsistencies is to perform a cross-venture audit that parses CI workflows and configurations, storing the resulting consolidated consistency report in VCMS for traceability.

Yes, you can detect missing Claude command presence across multiple venture repositories by running a cross-venture audit that parses local repositories to identify tooling drift and summarize consistency hotspots in a report.

Cross-venture audits are limited to parsing local repository configurations like package.json, tsconfig.json, and CI workflows, requiring a crane-console workspace and local repo access rather than analyzing remote or non-standard project structures.