arch-review-async

Reviews code changes against async architecture lenses covering infrastructure, queues, workers, and failure handling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing asynchronous code for architectural rule violations is slow and inconsistent when done by hand. This Skill automates a focused architecture review of the async layer—infrastructure, queues, workers, and park-vs-fail decisions—by applying a fixed catalog of lenses to a code change and producing a structured findings report. ## Core Features & Use Cases - Lens-Based Review: Judges code strictly against the lenses in the async lens file, deciding each as finding, pass, unverified, or not applicable, with severity taken from the lens. - Flexible Scope: Reviews the current branch's change, the whole repository, a git range, a single commit, or a path/glob, reading history with git show when the scope is not checked out. - Static Checker Integration: Runs the bundled arch-check tool first on working-tree scopes and treats its full-coverage lenses as decided, falling back to manual judgment when the checker cannot run. - Use Case: Before merging a pull request that adds a new queue consumer, run the review to catch missing consumer-side idempotency or a worker that fails instead of parking a poison message. ## Quick Start Ask the assistant to run an async architecture review of the current branch's changes and report any findings with file and line references.

Frequently Asked Questions about arch-review-async

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

FAQPage Schema
How do I review async code changes for architecture violations?▼

Run the review with no arguments to check the current branch's change against the async lenses, or pass a git range, commit, path, or the word all. The output is a Markdown report listing findings with file, line, severity, and a one-sentence fix.

What does the async architecture review check?▼

It checks infrastructure, worker roles, consumer-side idempotency, long-running orchestrations, correlation across handoffs, and park-versus-fail decisions. Each rule comes from a lens file, and the review never flags anything a lens does not name.

Can I review a specific commit or git range instead of the working tree?▼

Yes. Pass a commit SHA, tag, branch, or a range like main..HEAD, and the review reads each file at that ref using git show rather than the working tree. The static checker is skipped for historical scopes and every lens is judged manually.

What happens if the arch-check static checker cannot run?▼

The review notes the failure in the report's Scope line and judges every lens itself, including the ones the checker would have decided. The manual review acts as the checker's fallback, so the report is still complete.

How are documented exceptions and ADRs handled in the review?▼

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. Deviations appear on one line under the Deviations section and never lower a finding's severity.