arch-review

Reviews proposed changes against platform architecture documents and native-first rules.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill arch-review-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/arch-review
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill arch-review-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent way to evaluate whether proposed changes, PRs, or design decisions comply with their platform architecture, topology rules, and ADR governance before implementation proceeds. ## Core Features & Use Cases - Architecture Compliance Review: Evaluates changes against canonical documents such as platform maps, topology definitions, and stack overviews. - Native-First Enforcement: Flags bespoke implementations of components that should use native platform capabilities, such as model gateways, vector stores, or secret managers. - Structured Verdicts: Produces a standardized review output with APPROVED, CONCERNS, or BLOCKED verdicts plus actionable findings and ADR impact notes. - Use Case: Before merging a PR that introduces a custom caching layer, run this review to confirm whether the change violates the native-first rule and whether an ADR needs to be created or updated. ## Quick Start Ask the assistant to run an architecture review on your proposed changes or PR and evaluate them against the platform map, topology, and native-first rules.

Frequently Asked Questions about arch-review

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

FAQPage Schema
How do I review a PR for architecture compliance?

Invoke the architecture review with a description of the proposed changes. The review reads the canonical architecture documents and relevant ADRs, then returns a verdict of APPROVED, CONCERNS, or BLOCKED with specific findings and recommendations.

What is the native-first rule in architecture review?

The native-first rule prioritizes native platform capability over thin adapters, and adapters over bespoke implementations. Custom versions of model gateways, vector stores, observability dashboards, workflow engines, and similar components are flagged as violations.

When should I create or update an ADR?

Create or update an ADR when a change touches ADR-governed areas or alters platform direction. The review checks existing ADR normative clauses and reports any ADRs affected, created, or needing updates in its output.

Can the architecture review block or approve changes automatically?

No, the review findings are advisory only. It can flag anti-patterns, native-first violations, and recommend ADR updates, but it does not implement code, manage backlogs, or override human decisions.

What documents does the architecture review depend on?

The review depends on canonical architecture documents: the platform map, topology definition, and stack overview, typically under docs/architecture/, plus any relevant ADR files. These paths are repo-specific and should be updated after scaffolding.