deep-audit

A deep consistency audit identifies and fixes factual errors, code bugs, count mismatches, and cross-document inconsistencies. It deploys parallel specialist agents to examine guide content, hook code, skills, rules, and references across your entire repository.

Yes, you can automatically fix repository infrastructure errors by running an audit that loops until the repository is clean. The process iteratively identifies and rectifies factual errors, code bugs, and inconsistencies introduced during development.

The best way to ensure repository integrity before a release is to perform a comprehensive automated audit. This catches introduced errors by deeply checking guide accuracy, hook code quality, and cross-document consistency across your repository infrastructure.

Yes, the repository audit checks both code quality and content accuracy simultaneously. It launches parallel specialist agents dedicated to verifying guide content accuracy and analyzing hook code quality, alongside checking skills and rules consistency.

To resolve count mismatches and factual errors in your repository, execute a deep consistency audit. The automated process detects these specific issues alongside code bugs and cross-document inconsistencies, fixing them iteratively until clean.

You should run a deep consistency audit after making significant changes to skills or rules. Running it before a release ensures that any newly introduced errors, count mismatches, or cross-document inconsistencies are caught and fixed.