arch-review-om

Reviews Python code against Object Model architecture lenses and reports findings with severity.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a code change against an architecture guideline by hand is slow and inconsistent; this Skill automates a focused review of the Object Model rules (source of truth, mixins, immutability, identifiers, namespaces, pure rules) so violations are caught with file and line evidence. ## Core Features & Use Cases - Scoped review: Reviews the current branch change, a commit, a range, a path, or the whole repository, reading files from git history when needed. - Checker integration: Runs the bundled arch-check static checker first and judges only the lenses it cannot decide, avoiding duplicate work. - Structured report: Produces a Markdown report with findings ordered by severity, deviations backed by ADRs, and pass/unverified/not-applicable decisions for every lens. - Use Case: Before merging a pull request that touches domain entities, run this review to confirm immutability and pure-rule constraints still hold and get a citable findings list. ## Quick Start Ask the assistant to run an Object Model architecture review of the current branch change using the arch-review-om skill.

Frequently Asked Questions about arch-review-om

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

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

Run the review with no arguments to check the current branch's change against the default branch merge base. You can also pass a commit, a range like main..HEAD, a path, or the word all to set the scope explicitly.

What does the Object Model architecture review check?▼

It checks the Object Model lens group: the domain as source of truth, entity naming, mixins, immutability, identifiers, namespaces as swimlanes, and pure rules. Each lens is decided as finding, pass, unverified, or not applicable with file and line evidence.

Does the review work on code that is not checked out?▼

Yes. When the scope is a commit or a range, files are read from git history with git show rather than the working tree. The static checker is skipped in that case and every lens is judged directly.

Why does the review say the checker could not run?▼

The bundled arch-check checker requires Python 3.11 or newer and only reads the working tree. On older interpreters, exit code 2, or history-based scopes, the review notes this in the Scope line and judges every lens itself as the fallback.

How are documented architecture deviations handled in review findings?▼

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 the ADR never lowers the severity of other findings.