What is 'Noun Analysis' in this workflow?

It is an analytical technique where Claude catalogs domain objects (nouns) to determine which modules should exist and which functions belong where based on ownership.

How are the architectural changes verified?

Each change is processed through a dedicated QA agent that runs test suites, linters, and any custom manual verification steps you provide.

Does this skill make changes automatically?

No. The workflow is highly collaborative; it presents an architectural blueprint for your approval and refinement before any implementation begins.

How does review-arch differ from a standard refactor?

While standard refactoring focuses on local code quality like naming and complexity, review-arch performs a strategic analysis to rethink module boundaries and the overall project structure.

What happens if a structural change fails testing?

If an item fails QA verification three times, the changes for that specific module are reverted, and the workflow moves to the next item to maintain repository stability.

Architectural Review Workflow

Name: Architectural Review Workflow
Author: chrisallenlane

bychrisallenlane

•

Herramientas para Desarrolladores

Performs strategic codebase restructuring through noun-based domain analysis and collaborative blueprint implementation.

The Architectural Review skill provides a high-level workflow for evaluating and improving software architecture within Claude Code. Unlike tactical refactoring, this skill focuses on module boundaries and domain ownership by performing a 'noun analysis' to identify core responsibilities. It generates a comprehensive target blueprint, allows for interactive refinement with the user, and then executes changes using specialized language experts (SMEs). Every change is verified by an automated QA agent and committed atomically to ensure the codebase remains stable and well-organized.

Características Principales

0112 GitHub stars

02Automated dead code identification and removal for cleaner codebases

03Domain-driven Noun Analysis to identify and evaluate module responsibilities

04Collaborative blueprinting for planning structural changes before implementation

05Integrated QA verification cycles with support for custom testing instructions

06Language-specific Subject Matter Expert (SME) agents for precise refactoring

Casos de Uso

01Restructuring a growing project into clear, domain-driven modules

02Identifying and safely removing dead code across a complex repository

03Standardizing module boundaries and naming conventions to reduce technical debt

Características Principales

0112 GitHub stars

02Automated dead code identification and removal for cleaner codebases

03Domain-driven Noun Analysis to identify and evaluate module responsibilities

04Collaborative blueprinting for planning structural changes before implementation

05Integrated QA verification cycles with support for custom testing instructions

06Language-specific Subject Matter Expert (SME) agents for precise refactoring

Casos de Uso

01Restructuring a growing project into clear, domain-driven modules

02Identifying and safely removing dead code across a complex repository

03Standardizing module boundaries and naming conventions to reduce technical debt