inquisition

Audit codebases against architectural doctrines and return structured JSON reports.

2|Updated Mar 10, 2026

Search Tags:#automation #architecture #codebase #audit #compliance #reporting #doctrines

Ready to run

npx skills add https://github.com/ppryde/pip-skills --skill inquisition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inquisition
Source: https://github.com/ppryde/pip-skills/tree/main/plugins/puritan/skills/inquisition
Command: npx skills add https://github.com/ppryde/pip-skills --skill inquisition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits codebases against architectural doctrines to enforce codified decisions and catch design violations early.

Core Features & Use Cases

Discover and apply doctrines against your repository to identify violations and ensure consistency.
Support loading configuration (.architecture/config.yml) and discovering doctrines in skills/doctrines, enabling multi-doctrine checks across targets.
Provide structured reports and workflows to triage and resolve issues in PRs and code changes.

Quick Start

Run the inquisition against your repository to audit code against configured doctrines.

Frequently Asked Questions about inquisition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my codebase against architectural doctrines?▼

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.

What is a codebase architectural audit and how does it work?▼

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.

Can I run an architectural audit on only the changed files in a PR?▼

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.

Do I need a specific config file to automate codebase compliance reporting?▼

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.

What is the best way to enforce architectural compliance rules across a repository?▼

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.

How does the inquisition skill handle multiple doctrine files during a scan?▼

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.