arch-review-context

Reviews code changes against Context architecture lenses covering stages, scopes, authorization, and tenancy.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change for architectural rule violations around operator context, authorization, tenancy, and provenance is slow and inconsistent when done by hand. This Skill automates that review by judging a change against a fixed catalog of Context lenses and producing a structured findings report. ## Core Features & Use Cases - Lens-based review: Judges code against the Context lens file covering stages, scopes, OperatorContext, authorization, tenancy, and provenance, deciding each lens as finding, pass, unverified, or not applicable. - Flexible scope resolution: Reviews the current branch change, the whole repository, a commit range, a single commit, or a path, reading files from the working tree or from git history as appropriate. - Static checker integration: Runs the bundled arch-check checker first, adopts its fully covered lens decisions, and manually judges the lenses it cannot decide. - Use Case: Before merging a pull request that touches request scoping or tenant isolation, run this review to get a severity-ordered findings report with file and line evidence, plus a record of documented ADR deviations. ## Quick Start Ask the assistant to run an architecture review through the Context lenses on the current branch change.

Frequently Asked Questions about arch-review-context

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

FAQPage Schema
How do I review a code change for architecture rule violations?▼

Run the review with no arguments to judge the current branch's change since the merge base with the default branch. The skill reads the Context lens file, runs the arch-check static checker, and reports findings with file and line evidence.

What does the Context architecture review cover?▼

It covers stages, scopes, OperatorContext, authorization, tenancy, and provenance, drawn from guideline sections on the business, storage, network, and infrastructure layers. It only flags rules named in the Context lens file and never borrows rules from other lens groups.

Can I review a specific commit or path instead of the whole branch?▼

Yes. Pass a commit SHA, tag, or branch to review that commit's change, a range like main..HEAD, a path or glob, or the word all for the entire repository. Ranges and commits are read from git history, never the working tree.

Does the review require the arch-check static checker?▼

No, the checker is optional. When it cannot run, such as on a Python older than 3.11 or exit code 2, the review notes this in the Scope line and judges every lens manually as the checker's fallback.

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

A breach whose ADR quotes the rule and is cited next to the code is a documented exception, not a finding. It appears on one line under Deviations, and the lens is decided on the rest of the scope; an ADR never lowers a severity.

Why does a high-severity lens show as unverified instead of passed?▼

A high lens passes only on positive evidence: a named file proving compliance or a clean arch-check run. When the deciding evidence lies outside the review scope, the lens is reported as unverified with a note naming what would decide it.