arch-review-delivery

Review code changes against Delivery architecture lenses covering apps, deployment, and telemetry.

89|10|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/baristaze/swe_guidelines --skill arch-review-delivery-baristaze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-review-delivery
Source: https://github.com/baristaze/swe_guidelines/tree/main/skills/arch-review-delivery
Command: npx skills add https://github.com/baristaze/swe_guidelines --skill arch-review-delivery-baristaze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change for architectural consistency across apps, deployment, repo layout, client architecture, telemetry, and conventions is slow and easy to do inconsistently. This Skill applies the Delivery group of architecture lenses to a change and produces a structured findings report. ## Core Features & Use Cases - Scoped review: Review the current branch's change, the whole repository, a commit range, a single commit, or a path, with files read in full including their neighbors. - Checker integration: Runs the bundled arch-check static checker first, adopts its findings for fully covered lenses, and judges the remaining lenses by reading the code. - Structured report: Outputs findings with severity, file and line, deviations backed by ADRs, plus passed, unverified, and not-applicable lens lists. - Use Case: Before merging a pull request that touches deployment configuration and logging, run this review to catch breaches of the Delivery rules and document any accepted deviations. ## Quick Start Ask the assistant to run an architecture review of the current branch through the Delivery lenses and report any findings.

Frequently Asked Questions about arch-review-delivery

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

FAQPage Schema
How do I review a code change against architecture rules?▼

Run the review with no arguments to check the current branch's change against the default branch, or pass a range, commit, or path. The skill reads the lens file, runs the static checker, judges remaining lenses, and reports findings with file and line.

What does the Delivery architecture review cover?▼

It covers apps, deployment, monorepo folder structure, client app architecture, logs and telemetry, cross-cutting conventions, and technology substitutions. Each rule is a lens with an id, severity, and explicit violation criteria.

Can I review a whole repository or a single commit?▼

Yes. Pass the word 'all' for every non-ignored file, a range like main..HEAD, a commit SHA or tag, or a path or glob. Ranges and commits are read from git history, never from the working tree.

What happens if the static checker cannot run?▼

If Python is older than 3.11 or the checker exits with code 2, the review notes this in the Scope line and judges every lens manually by reading the code. The review acts as the checker's fallback.

How are documented exceptions to architecture rules handled?▼

A breach backed by an ADR that quotes the rule and is cited next to the code is recorded as a deviation, not a finding. It appears on one line under Deviations and never lowers a severity.

Does the architecture review modify my code?▼

No. The skill only reads and reports; it never edits, stages, or commits anything. Its output is a Markdown report with findings, deviations, passed, unverified, and not-applicable lenses.