Extension & CLI Overview

What ArchPilot does

ArchPilot helps teams make architecture explicit, validate it consistently, and keep architectural drift visible before problems spread through a codebase.

It combines architecture-as-code configuration, deterministic validation, dependency checks, findings, scores, review artifacts, and optional governance upload into one workflow that starts locally.

• Run architecture validation in VS Code and the CLI.
• Detect and explain dependency boundary problems, contract violations, and structural drift.
• Generate findings, architecture scores, readiness signals, change risk, and governance risk from the same validation run.
• Carry the same architecture validation flow into pull requests and CI.

Why local validation matters

ArchPilot is designed so architecture validation happens locally first. Developers can review findings and fix issues before they push or open a pull request.

This keeps software architecture review practical: the same rules run on a laptop, in VS Code, and in CI, without depending on a hosted validator to produce the core result.

What you can do next

1. Start with Getting Started to understand the first-run workflow.
2. Use Smart Init to see how ArchPilot detects repository structure and proposes architecture metadata.
3. Open Validation & Findings to understand scores, readiness, risk, and rule output.
4. Read Governance Upload if you want to connect local ArchPilot validation to ArchPilot Cloud.

Plan note

Local validation in the VS Code extension and CLI is available on all plans.

Manual governance upload is available on all plans. Automatic CI upload to Cloud on main is available on paid plans.