build-loop:architecture-review

Review codebase architecture for system flow, component communication, and documentation drift.

1|Updated Apr 6, 2026

Search Tags:#codebase analysis #architecture review #architecture validation #system integrity #cross-layer analysis

Ready to run

npx skills add https://github.com/tyroneross/build-loop --skill build-loop-architecture-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-loop:architecture-review
Source: https://github.com/tyroneross/build-loop/tree/main/skills/architecture/review
Command: npx skills add https://github.com/tyroneross/build-loop --skill build-loop-architecture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for in-depth architectural review during complex code changes, ensuring system integrity and adherence to best practices.

Core Features & Use Cases

Cross-Layer Analysis: Reviews system flow, component connections, and documentation for consistency across different layers.
System Flow Analysis: Assesses how data moves through the system from input to output.
Component Communication: Validates API contracts and connection patterns between components.
Documentation Drift: Ensures that documentation reflects the actual code.
Use Case: When performing a large refactor or cross-layer change, use this Skill to validate the architecture before merging.

Quick Start

Run the skill with the command: build-loop:architecture-review --all

Frequently Asked Questions about build-loop:architecture-review

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

FAQPage Schema

How do I perform a cross-layer architecture review before merging a large refactor?▼

A cross-layer architecture review validates system flow, component communication, and documentation drift by tracing connections across the codebase. It requires a well-defined architecture data model and codebase access to ensure system integrity before merging large refactors.

What is documentation drift and how does an architecture validation check detect it?▼

Documentation drift occurs when project documentation no longer reflects the actual codebase implementation. Architecture validation detects this by comparing documented component connections and system flow against the actual code to ensure consistency across all layers.

Does system flow analysis require a predefined architecture data model to trace component connections?▼

Yes, system flow analysis requires a well-defined architecture data model to accurately trace component connections and assess data movement. The model provides the structural baseline needed to perform impact analysis and validate API contracts across the codebase.

How do I validate API contracts and component communication patterns across different layers?▼

To validate API contracts and component communication, run a comprehensive architectural review using the command `build-loop:architecture-review --all`. This assesses how components interact, checks connection patterns, and ensures system flow remains consistent across all layers.

What's the best way to check codebase integrity and system flow for complex code changes?▼

The best way to check codebase integrity is executing a comprehensive architectural review that analyzes cross-layer system flow and component communication. This validates that data moves correctly from input to output and confirms adherence to structural best practices.