arch-review

Audits codebase structure against the architect blueprint for orphaned work, deviations, and risks.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill arch-review-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/arch-review
Command: npx skills add https://github.com/Vimurai/ai-os --skill arch-review-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a codebase grows under multiple agents or contributors, implemented features can drift away from the architectural blueprint, leaving orphaned code, unimplemented sections, and undocumented dependencies. This Skill performs a structured architectural audit so misalignment is caught before a major commit. ## Core Features & Use Cases - Blueprint Alignment Audit: Classifies each implemented feature in src/ as ALIGNED, ORPHANED, or DEVIATED relative to architect.md. - Coverage and Ambiguity Checks: Flags blueprint sections with no implementation and vague sections that are unsafe to implement. - Dependency and Risk Review: Verifies new dependencies have DECISIONS.md entries and produces a Top 3 architectural risks list with recommended P-## tasks. - Use Case: Before merging a large feature branch, run the audit to confirm every new module is covered by the blueprint and record an ARCH_AUDIT stamp in the project review log via MCP. ## Quick Start Ask the AI to run an architectural review auditing the current codebase against the blueprint before the next major commit.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I check if my codebase matches its architecture documentation?▼

Run an architectural audit that compares each implemented feature in the source directory against sections of the blueprint document. Features are classified as aligned, orphaned, or deviated, and missing implementations are flagged as candidates for new engineering tasks.

What does an architectural review audit report include?▼

The report contains an alignment summary, coverage gaps, ambiguous blueprint sections, the top three architectural risks with mitigations, and recommended planning tasks. It is output as structured Markdown and recorded as an ARCH_AUDIT stamp via the task-synchronizer MCP tool.

Can the architectural audit modify source code or review logs?▼

No. The audit is read-only for source code and must not write to src/ or append directly to REVIEWS.md, which is a generated view. Findings are recorded only through the MCP add_stamp interface to keep state consistent.

When should I run an architecture alignment audit?▼

Run it before major commits, when the user requests an architectural review, or when checking blueprint alignment after significant implementation work. It is most useful when multiple agents or contributors have changed the codebase since the last audit.

Why does the audit only scan the src directory structure instead of reading files?▼

The audit operates at the architectural level, so it compares the directory structure against blueprint sections rather than reviewing line-level code. This keeps the review fast and focused on alignment, coverage, and risk rather than implementation detail.