Architecture Review

When reviewing code that involves architectural decisions, new modules, data flow changes, or system design. Use when the PR introduces new services, changes API boundaries, modifies database schemas, adds new dependencies, or restructures significant portions of the codebase. Also use when the user says 'review the architecture,' 'is this the right approach,' or 'design review.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add 0xranx/agentbrief --skill architecture-review
Manual install
git clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/code-reviewer/skills/architecture-review ~/.claude/skills/architecture-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Architecture Review

You are a staff-level engineer reviewing architectural decisions. Your job is to catch design issues that unit tests and linters cannot: wrong abstractions, leaky boundaries, missing edge cases, and scaling traps.

## Review Process

### 1. Understand the Intent

Before reviewing code, understand *what problem is being solved*:

- Read the PR description, linked issue, or spec
- Identify the core requirement vs. incidental complexity
- Ask: "Is this the simplest approach that solves the actual problem?"

### 2. Data Flow Analysis

Trace data from entry to exit:

1. **Input boundary** — Where does data enter? Is it validated at the edge?
2. **Transformation chain** — How many layers does data pass through? Each hop is a potential failure point
3. **Storage** — What's persisted? Is the schema forward-compatible?
4. **Output boundary** — What leaves the system? Is it sanitized?

Flag any case where data is transformed more than 3 times before reaching its destination.

### 3. Dependency Direction Check

- Dependencies should point inward (domain ← application ← infrastructure)
- Flag any case where domain logic imports from infrastructure
- Flag circular dependencies between modules
- Flag "god modules" that everything imports from

### 4. Error & Edge Case Audit

For each new code path, check:

- What happens on timeout?
- What happens on partial failure (e.g., DB write succeeds but cache update fails)?
Read the full skill on GitHub

Details

Skill name
architecture-review
Path
briefs/code-reviewer/skills/architecture-review/SKILL.md
License
MIT
Repo updated
28 March 2026

FAQ

What does the Architecture Review skill do?

When reviewing code that involves architectural decisions, new modules, data flow changes, or system design. Use when the PR introduces new services, changes API boundaries, modifies database schemas, adds new dependencies, or restructures significant portions of the codebase. Also use when the user says 'review the architecture,' 'is this the right approach,' or 'design review.

How do I install the Architecture Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill architecture-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Architecture Review popular?

It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.

Related skills

Typescript Advanced Types

43

0xranx/agentbrief

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Software Development

Analytics Setup

43

0xranx/agentbrief

When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.

Data & Analytics

API Documentation

43

0xranx/agentbrief

Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.

Software Development

Brainstorming

43

0xranx/agentbrief

Design-first approach that generates and evaluates multiple alternatives before coding

Software Development

Doubt Driven Development

48

frankxai/claude-skills-library

Cross-examine a non-trivial decision with a fresh, adversarial reviewer before it stands, ideally a different model family. Use before committing branching logic, a boundary change, a safety or idempotence claim, an irreversible step (deploy, migration, merge, public claim), or any confident statement that is cheaper to disprove now than to debug later.

Software Development

Acos Meta

48

frankxai/claude-skills-library

ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.