architecture-review

Review codebase architecture for coupling, duplication, and integration fit with evidence-based verdicts.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/FluxonLab/Skillry --skill architecture-review-fluxonlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/FluxonLab/Skillry/tree/main/plugins/core-operations/skills/03-architecture-review
Command: npx skills add https://github.com/FluxonLab/Skillry --skill architecture-review-fluxonlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams struggle to decide whether to keep, adapt, or replace existing code structures without objective evidence, often leading to unnecessary rewrites, parallel implementations, and architectural drift. ## Core Features & Use Cases - Dependency and Cycle Analysis: Maps module boundaries, detects circular dependencies, and flags layer inversions using tools like madge and ripgrep. - Duplication and Coupling Detection: Identifies parallel HTTP clients, competing state stores, god modules, and high-churn high fan-in files. - Keep/Adapt/Replace Decisions with ADRs: Produces justified verdicts per component and records decisions as Architecture Decision Records via the absorbed adr-generator reference. - Use Case: Before a large refactor touching multiple modules, run this review to confirm the change follows existing dependency direction, surface the riskiest files, and document the decision as an ADR. ## Quick Start Review the architecture of the src directory and tell me which components to keep, adapt, or replace with file-level evidence.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I detect circular dependencies in a TypeScript project?▼

Run npx madge --circular --extensions ts,tsx,js,jsx on your source directory to list circular dependency chains. You can also use madge --orphans to find unreferenced modules that may indicate dead code.

How to decide between refactoring and rewriting a codebase?▼

Recommend replacement only when the existing structure provably blocks the goal, adapting it costs more than replacing it, and a staged migration with rollback exists. Otherwise adapt in place behind an existing seam, which is the lowest-risk default.

What is an Architecture Decision Record and when should I write one?▼

An ADR is a markdown document capturing the context, decision, alternatives, and consequences of a significant architectural choice. Write one when a decision like a database or framework selection is made or proposed, not for trivial or purely operational choices.

How do I find god modules and high-risk files in my repo?▼

Use ripgrep to count local imports per module and sort by frequency to find god-module candidates, then combine with git log churn over the last six months. Files with both high fan-in and high churn are the highest refactor risk.

When should I not run an architecture review?▼

Skip it when the task is unrelated to core operations, requires production deploys or secret disclosure, or when you first need a structural map from a repo-diagnostics pass. A narrower existing project instruction may also already cover the need.