inquisition

To audit your codebase against architectural doctrines, the skill loads configuration from `.architecture/config.yml`, discovers rules in `skills/doctrines`, and executes scans to return structured JSON reports identifying design violations.

A codebase architectural audit automatically checks your repository against codified design decisions. It discovers doctrine files and executes subagents to evaluate changed files or full projects, producing structured reports to catch violations early.

Yes, you can run an architectural audit on changed files. The skill supports both changed-files and full-project scans across multiple doctrine files to triage and resolve issues in PRs and code changes.

Yes, you need a `.architecture/config.yml` file to automate codebase compliance reporting. The skill loads targets, decision rules, and doctrines from this configuration path to execute its automated audit workflows.

The best way to enforce architectural compliance is to define doctrines in `skills/doctrines` and configure targets in `.architecture/config.yml`. The skill automates applying these rules to identify violations and ensure consistency.

The inquisition skill handles multiple doctrine files by discovering them in the `skills/doctrines` directory and executing subagents to apply each doctrine against configured targets, returning a consolidated structured JSON report.