skills.rest
cesau78
cesau78COMMUNITY
Explore all skills by this author →
GitHub

review-architecture

Audits code modules for duplication, boundary issues, and refactor opportunities.

Updated Apr 2, 2026
Search Tags:#architecture#modularity#refactor#duplication#code-review#boundaries
One-click install
npx skills add https://github.com/cesau78/cesau-skills --skill review-architecture-cesau78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-architecture
Source: https://github.com/cesau78/cesau-skills/tree/main/review-architecture
Command: npx skills add https://github.com/cesau78/cesau-skills --skill review-architecture-cesau78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code structure for duplication, unclear boundaries, and refactor opportunities that consolidate logic and reduce surface area. Use when reviewing a diff or module before push, when the user asks for a DRY or architecture pass, or when skills-advisor recommends this lens.

Core Features & Use Cases

  • Duplication — surface parallel components, hooks, or utilities that differ only by data or labels.
  • Boundaries — identify ownership and module placement, separating shared logic from page-specific code.
  • Naming & Modules — clarify abstractions and ownership to reduce friction during integration.
  • Use Case — perform an architecture review on a diff to propose consolidation before merge.

Quick Start

Run the review-architecture lens on the target module to surface actionable consolidation opportunities.

Frequently Asked Questions about review-architecture

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

FAQPage Schema
How do I identify code duplication and boundary issues before a merge?▼

An architecture review identifies duplications by surfacing parallel components or utilities that differ only by data. It separates shared logic from page-specific code to clarify module boundaries and propose DRY refactors.

What is the best way to perform a DRY refactor on a module?▼

Perform a DRY refactor by auditing module ownership and naming abstractions. This surfaces consolidation opportunities that reduce code surface area and clarify boundaries for smoother integration.

When do I need an architecture review for my code?▼

You need an architecture review when auditing a diff or module before a commit, when requesting a DRY pass to reduce surface area, or when unclear boundaries and naming abstractions create friction during integration.

Does this architecture review evaluate naming and module ownership?▼

Yes, this architecture review evaluates naming and module ownership. It clarifies abstractions and separates shared logic from page-specific code to produce concrete, actionable consolidation recommendations.

Related Skills

Explore More Software Engineering Skills→
inernoroinernoro
2

scope-check

Audit branch changes against main and classify files as owned, shared, or foreign.

Community
Intermediate
T1nker-1220T1nker-1220

clean-architecture-principles

Enforce clean-architecture principles with DRY, YAGNI, KISS, and Law of Demeter checks.

Community
Basic
benediktmsbenediktms

neocortex

Evaluate code changes for module boundaries, coupling, and abstraction fit.

Community
Advanced
gekko68gekko68

bash-executor

Execute Bash commands with validation, dry-run previews, and timeout protection.

Community
Advanced