verify-adoption

To check if code aligns with project standards, validate code and configuration against project adoption files. This detects non-conformities by scanning the codebase against defined architecture, security, and coding guidelines.

To verify a Pull Request, scan the changes against your project's adoption documents for specified scopes like tech-stack and infrastructure. This compliance audit reports deviations without modifying the code.

The best way to audit codebase compliance without modifying files is to use a detection-only validation process. It scans configurations against adoption guidelines and reports findings per area, routing resolution to developers.

Yes, you can scan your codebase for non-conformities across multiple scopes. By specifying scopes like coding-standards and infrastructure, the validation process detects deviations and reports them per area for manual developer action.

Code compliance validation only reports non-conformities and does not fix issues automatically. It detects deviations from adoption documents and routes the resolution to appropriate skills or manual developer action.

You should run a full project scope compliance audit before merging to ensure changes adhere to established guidelines and architecture. Scanning with all scopes provides a comprehensive conformity report without altering the code.