arch-review

Analyze codebases with noun analysis and produce a target architecture blueprint.

18|4|Updated Jan 29, 2026

Search Tags:#workflow #architecture #codebase #qa #analysis #refactor #blueprint

Ready to run

npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill arch-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arch-review
Source: https://github.com/chrisallenlane/claude-swe-workflows/tree/main/skills/arch-review
Command: npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill arch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams rethink and reorganize codebases by analyzing architecture, producing a coherent target blueprint, and guiding collaborative decision-making before implementation.

Core Features & Use Cases

Noun-analysis driven domain modeling to identify module ownership and boundaries.
Atomic blueprint-driven changes coordinated through SMEs and QA for safe refactoring.
Interactive planning and documentation updates to keep stakeholders aligned.

Quick Start

Run /arch-review to analyze the codebase, review the proposed blueprint with your team, and decide how to proceed.

Frequently Asked Questions about arch-review

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

FAQPage Schema

How do I identify architectural boundaries in an existing codebase for refactoring?▼

You can identify architectural boundaries in a codebase by running an interactive noun-analysis workflow. This process examines the codebase to extract domain models, which are then used to map out module ownership and define a target architecture blueprint for refactoring.

What is noun analysis and how does it help with codebase architecture review?▼

Noun analysis is a domain modeling technique used during an architecture review to identify key entities within a codebase. It helps uncover natural module ownership and architectural boundaries, which are then used to produce a coherent target architecture blueprint.

How do I plan and execute a codebase refactor safely with stakeholder collaboration?▼

You can plan a codebase refactor safely by using an interactive workflow that proposes a target blueprint for collaborative review. Once refined, changes are committed atomically through Subject Matter Experts and QA verification to ensure safe implementation.

Can I remove dead code during an architectural improvement workflow?▼

Yes, you can remove dead code during an architectural improvement workflow. The interactive process guides scoping, planning, and dead-code removal alongside iterative blueprint execution, ensuring that structural cleanup is safely integrated into the refactor.

Does blueprint-driven refactoring require QA verification before committing changes?▼

Yes, blueprint-driven refactoring requires QA verification before committing changes. The workflow coordinates atomic changes through Subject Matter Experts and QA to ensure that the architectural improvements are safe and meet quality standards before implementation.

What is the best way to document architectural changes after a codebase refactor?▼

The best way to document architectural changes after a refactor is to use a workflow that automatically updates documentation upon completion. This ensures that stakeholders remain aligned with the new target architecture blueprint and implemented modifications.