arch-code-review

Validate architectural diffs against canonical YAML artifacts for consistency and governance.

80|2|Updated May 14, 2026
One-click install
npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill arch-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-code-review
Source: https://github.com/PriNova/pi-agent-codebase-workflows/tree/main/skills/arch-code-review
Command: npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill arch-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture-aware review ensures diffs against canonical structured YAML artifacts are evaluated for correctness, consistency, and compliance with governance rules, preventing drift from intended architecture.

Core Features & Use Cases

  • Read-only review of architecture across the resolved structured docs root.
  • Enforces ownership, contracts, invariants, and risk controls.
  • Validate reference integrity and deterministic formatting of artifacts.
  • Use Case: A repo undergoing changes to contracts and data-flow requires a secure, artifact-driven review before merge.

Quick Start

Review the latest diff against architecture.yaml and related artifacts to verify contract adherence.

Frequently Asked Questions about arch-code-review

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

FAQPage Schema
How do I validate architecture diffs against canonical YAML artifacts?▼

Architecture-aware review validates architecture diffs against canonical YAML artifacts by operating in read-only mode across the structured docs root, checking stable ID usage, evidence collection, and deterministic YAML formatting.

What is architecture-aware code review for structured artifacts?▼

Architecture-aware code review for structured artifacts evaluates architectural diffs against canonical YAML files to ensure correctness, consistency, and compliance with governance rules, preventing drift from intended architecture.

How do I enforce architecture contracts and invariants during a code review?▼

You enforce architecture contracts and invariants by applying a read-only review across the resolved structured docs root, verifying ownership, cross-scope references, and risk controls against canonical YAML artifacts.

Can I review architecture YAML artifacts without modifying the repository?▼

Yes, architecture-aware review operates in read-only mode across the resolved structured docs root, validating reference integrity and deterministic formatting without modifying the repository or legacy prose docs.

When do I need to use canonical YAML artifacts for architecture governance?▼

You need canonical YAML artifacts for architecture governance when a repository undergoing changes to contracts and data-flow requires a secure, artifact-driven review to verify ownership, invariants, and risk controls before merge.

Does architecture review work with legacy prose documentation?▼

No, architecture review specifically excludes legacy prose docs, focusing exclusively on validating structured YAML artifacts within the resolved structured docs root to maintain deterministic formatting and reference integrity.