audit

Evaluate codebase architecture for modularity, coupling, and misplaced boundaries, then write an audit report.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill audit-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/kieranpotts/skills/tree/main/skills/audit
Command: npx skills add https://github.com/kieranpotts/skills --skill audit-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases drift over time: modules become shallow wrappers, dependencies tangle, and structural boundaries leak. This Skill performs an unbiased, independent architectural audit of the as-built system and records prioritized findings in a report, without touching any code. ## Core Features & Use Cases - Independent structural review: The agent deliberately ignores existing design docs and decision records, judging the code and data schema on their own merits to avoid bias from settled trade-offs. - Smell detection with evidence: Flags shallow modules, tangled dependencies, single-caller abstractions, inverted dependencies, and leaky boundaries, with every finding citing specific files and lines. - Prioritized report output: Findings are ranked by impact divided by effort and written to a configurable audit report store, ready to feed a downstream refactor. - Use Case: After a large changeset lands on the main branch, run the audit against the repository at a pinned commit to check whether module boundaries still hold, then hand the report to a refactoring agent. ## Quick Start Audit this codebase and file an architectural audit report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I run an architectural audit on a codebase?▼

Invoke the audit with a phrase like "audit this codebase" or "do an architectural audit". You can name a target path or repository URL and pin a specific commit; otherwise the current repository at its checked-out revision is audited.

What does an architecture audit report check for?▼

The audit checks module depth, boundary placement and leakage, tangled dependencies, single-caller abstractions, inverted dependencies, and misnamed abstractions. Every finding must cite specific files and lines, and findings are prioritized by impact divided by effort.

Does the audit skill modify my code or repository?▼

No. The audit is discovery-only: the audited codebase must remain byte-for-byte unchanged, with no commits, branches, issues, or pull requests raised. The only output is a single report written to the resolved audit reports store.

Can the audit detect security or performance problems?▼

No. Security, privacy, and runtime performance findings are explicitly out of scope and must not appear in the report. Those concerns are handled by separate exercises such as a security probe with its own methods.

Why does the audit ignore existing design documentation?▼

Deliberate blindness to design docs and decision records keeps the review unbiased, so the agent forms judgment from the code and data structures alone. The trade-off is some noise from retreading settled trade-offs.

When should I not run an architecture audit?▼

Avoid running it on every commit, especially in continuous integration, since it is open-ended analysis best suited to a premium reasoning model. Schedule it periodically, after large changesets, or as a release preflight step.