skills.rest
xinbenlv
xinbenlvCOMMUNITY
Explore all skills by this author →
Website𝕏@ZainanZhouGitHub

codereview-architect

Analyze blast radius and trace dependencies across codebases to enforce architectural boundaries.

8|Updated Jan 14, 2026
Search Tags:#architecture#codebase#dependencies#code-review#analyze#blast radius
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codereview-architect
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/codereview-architect
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams understand how code changes ripple through a codebase, enabling safer refactors and architectural decisions.

Core Features & Use Cases

  • Blast Radius Analysis: Identify all impacted modules and code paths.
  • Dependency Tracing: Map usages and dependencies across layers.
  • Architectural Consistency: Enforce layering and boundary rules during changes.
  • Use Case: When reviewing core utilities, shared libraries, or database models, apply this Skill to anticipate ripple effects.

Quick Start

Activate codereview-architect when reviewing a PR that touches core utilities, shared libraries, or database models. Example: activate codereview-architect on PR #123 Example: activate codereview-architect on commit abc1234

Frequently Asked Questions about codereview-architect

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

FAQPage Schema
How do I analyze the blast radius of code changes across a codebase?▼

Blast radius analysis identifies impacted modules and code paths by tracing architectural dependencies. It maps impact paths across shared libraries and database models to prevent ripple effects during refactoring.

When do I need to trace dependencies for architectural consistency?▼

Trace dependencies when reviewing changes to core utilities, shared libraries, database models, or configurations. This enforces layering and boundary rules to anticipate ripple effects before merging code.

How do I map usages and dependencies across code layers during a PR review?▼

Mapping usages across layers requires tracing architectural dependencies within the codebase. Apply deep graph analysis during PR reviews to enforce architectural boundaries and prevent unintended ripple effects.

Can I enforce architectural boundaries for shared libraries and database models?▼

Yes, architectural boundaries are enforced by mapping impact paths and tracing dependencies. Analyzing blast radius during reviews of shared libraries and database models ensures structural consistency and prevents ripple effects.

What is the best way to prevent ripple effects when refactoring core utilities?▼

Preventing ripple effects requires analyzing blast radius and dependency usages across the codebase. Mapping impact paths for core utilities ensures safer refactors and enforces architectural layering boundaries.

Related Skills

Explore More Software Engineering Skills→
swannysecswannysec
2

impact-flow

Analyze Python and TypeScript codebases to map dependencies, blast radius, health, and execution flow.

Community
Advanced
t-hasuiket-hasuike

project-guide

Generate a structured reference guide for project documentation during legacy-system investigations.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
ByronWilliamsCPAByronWilliamsCPA

codebase-memory

Trace code dependencies and call chains using a pre-built knowledge graph.

Official
Intermediate