arch-review-contracts

Reviews code against Contracts architecture lenses covering interfaces, injection, and wiring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the architecture review of a code change through one specific perspective: the Contracts lenses (interfaces, dependency injection, and wiring), producing a structured findings report instead of an ad-hoc manual review. ## Core Features & Use Cases - Scoped review input: Reviews the current branch's change, a commit, a range, a path, or the whole repository, resolving the scope through git commands. - Static checker integration: Runs the bundled arch-check checker on working-tree scopes and merges its findings with manual lens judgments, falling back to full manual review when the checker cannot run. - Structured report: Emits a fixed-format Markdown report with findings (severity, file, line, fix), ADR-documented deviations, and pass/unverified/not-applicable lens tallies. - Use Case: Before merging a pull request that adds a new service interface, run this review to verify the interface, its injection, and its wiring in the app container comply with the guideline's Contracts rules. ## Quick Start Ask the assistant to run the arch-review-contracts skill on the current branch to check interfaces, injection, and wiring against the Contracts lenses.

Frequently Asked Questions about arch-review-contracts

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

FAQPage Schema
How do I review a pull request for architecture contract violations?▼

Run the skill with no arguments to review the current branch's change against the default branch merge base. It checks interfaces, injection, and wiring lenses and reports findings with file, line, severity, and a suggested fix.

What does the Contracts architecture review check?▼

It checks the Contracts lens group: Interfaces, Separation of Layers, The Business Layer, The Network Layer (service interfaces and impls, direction of calls), and the App Container convention. Each lens is decided as finding, pass, unverified, or not applicable.

Can I review a specific commit or file path instead of a 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 whole repository. Ranges and commits are read from git history, not the working tree.

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

No. The checker runs first on working-tree scopes when Python 3.11+ is available, deciding fully covered lenses. When it cannot run, the skill says so in the Scope line and judges every lens manually as the checker's fallback.

How are documented architecture deviations handled in the report?▼

A breach backed by an ADR that 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.