code-reviewer

To audit code changes for financial accuracy, run the code-reviewer audit on PRs and commits affecting monetary calculations, verifying decimal handling, rounding, and precision across modules using the four audit pillars.

Enforcing security guidelines on external communications involves operational integrity checks that verify API usage and network stability against security references, ensuring compliance before production deployment.

Preventing metadata drift in data pipelines requires data integrity governance checks that monitor metadata across data_engine and master pipelines, verifying consistent alignment and preventing misalignment during code reviews.

Yes, you can require root-cause fixes over quick patches during automated code reviews by applying the four audit pillars, consulting FINANCIAL_AUDIT.md and SECURITY_GUIDE.md, and enforcing root-cause resolution on all flagged issues.

Yes, the code-reviewer audit works without external dependencies, relying solely on internal references like FINANCIAL_AUDIT.md and SECURITY_GUIDE.md to perform audits across all PRs and commits affecting financial calculations and data integrity.

You need to run a financial accuracy audit whenever code changes affect financial calculations, external communications, or metadata integrity, ensuring decimal handling, rounding, and network stability remain precise across modules.