compliance-officer

Code compliance auditing scans repository content for rule references and enforces adherence to immutable rules defined in `.agent/rules/*.md` files. It logs pass/fail outcomes in a structured report, useful for CI checks, code reviews, and automated audits across the repository.

Automated code governance enforcement works by scanning repository content against immutable rules defined in `.agent/rules/*.md` files. It identifies missing or violated rules, warns about them, and generates remediation guidance for maintainers to ensure consistency and safety before changes are merged.

The best way to check repository rules before merging is running a full audit to validate the codebase against the official `.agent/rules/*.md` set. It produces a clear pass/fail report, ensuring consistency, safety, and adherence before changes are merged without executing code.

Yes, you need to define rules as Markdown files located within the `.agent/rules/*.md` directory. The compliance audit script scans this specific directory to load the immutable rule set and verify that repository content adheres to it before generating a report.

Yes, you can use this audit script to generate remediation guidance. It identifies missing or violated rules, warns about them, and logs pass/fail outcomes in a structured report, providing specific guidance for maintainers to fix deviations from the `.agent/rules/*.md` set.

A limitation of using Markdown files for code review compliance checks is that rules must be manually defined and maintained in `.agent/rules/*.md`. The script enforces these rules without executing code, so it cannot verify runtime behavior or dynamic logic, only static repository content.