What is the primary purpose of the Code Review Architect skill?

It is designed to help Claude identify how a change in one part of the codebase affects other areas, focusing on dependencies and architectural integrity.

Does this skill help with Clean Architecture?

Yes, it specifically checks for architectural layer violations, such as domain logic depending on infrastructure or controllers bypassing service layers.

Can it detect breaking changes in APIs?

Absolutely; it analyzes interface contracts, return types, and parameter changes to ensure all callers are updated or backwards compatibility is maintained.

When should I use this skill?

Invoke this skill when modifying core utilities, shared libraries, database models, or public APIs where the impact of a change might not be immediately obvious.

Code Review Architect

Name: Code Review Architect
Author: xinbenlv

byxinbenlv

Collaboration Tools

Analyzes the blast radius and architectural consistency of code changes using deep codebase context.

About

The Code Review Architect skill acts as a senior system specialist for Claude, providing deep-context analysis of how changes ripple through a software project. It moves beyond simple syntax checking to understand dependency graphs, identify potential breaking changes in core utilities, and enforce architectural patterns like layer boundaries and library standardization. This skill is essential for maintaining large-scale codebases where a single modification in a shared module can have unintended consequences across multiple files, ensuring long-term maintainability and system stability.

Key Features

Blast radius analysis to track how changes affect downstream dependencies
Detection of circular dependencies and architectural layer violations
Safety assessments for database migrations and state management
Interface contract verification for return types and parameter structures
0 GitHub stars
Standardization checks for library usage and naming conventions

Use Cases

Validating database schema migrations and data model changes
Reviewing modifications to core utility functions or shared libraries
Ensuring new features adhere to existing architectural patterns

About

Key Features

Blast radius analysis to track how changes affect downstream dependencies
Detection of circular dependencies and architectural layer violations
Safety assessments for database migrations and state management
Interface contract verification for return types and parameter structures
0 GitHub stars
Standardization checks for library usage and naming conventions

Use Cases

Validating database schema migrations and data model changes
Reviewing modifications to core utility functions or shared libraries
Ensuring new features adhere to existing architectural patterns