rb-architecture-review

Analyze codebase structure to identify architectural risks and coupling issues.

Updated Jul 2, 2026

Search Tags:#architecture #refactoring #code-review #software-design #technical-debt

Ready to run

npx skills add https://github.com/richardmbailey/rb-skills --skill rb-architecture-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rb-architecture-review
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-architecture-review
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-architecture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses structural decay, hidden technical debt, and unclear boundaries in a codebase by providing a systematic, objective review of its architecture.

Core Features & Use Cases

Structural Analysis: Identifies shallow modules, circular dependencies, and poor test seams that hinder maintainability.
Risk Assessment: Prioritizes architectural risks based on impact and likelihood to guide refactoring efforts.
Use Case: Use this skill when you are preparing to scale a system or when you suspect that current coupling is preventing the implementation of new features.

Quick Start

Invoke the rb-architecture-review skill to analyze the current repository structure and generate a prioritized refactoring plan.

Frequently Asked Questions about rb-architecture-review

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

FAQPage Schema

How do I identify architectural risks and coupling issues in my codebase?▼

To identify architectural risks, perform a structural critique that maps dependencies, detects circular references, and evaluates module boundaries. This process highlights shallow modules and poor test seams that hinder maintainability.

What is the best way to assess technical debt before scaling a software system?▼

The best way to assess technical debt before scaling is conducting a systematic structural analysis to prioritize risks based on impact and likelihood. This reveals hidden boundaries and coupling problems that prevent new feature implementation.

How do I generate a prioritized refactoring plan for poor software design?▼

To generate a prioritized refactoring plan for poor software design, analyze the repository structure to pinpoint shallow modules and circular dependencies. This yields a strategy targeting the most critical structural decay first.

When do I need an architecture review for my software engineering project?▼

You need an architecture review when preparing to scale a system or suspecting current coupling prevents new feature implementation. It evaluates modularity, maps dependencies, and checks if state machines and orchestration layers are necessary.

Does a structural critique respect existing project conventions during a code review?▼

A structural critique requires adherence to established project conventions while evaluating the codebase. It systematically assesses modularity and dependency mapping without overriding your existing software design standards.

Why does hidden technical debt make software refactoring difficult to plan?▼

Hidden technical debt makes refactoring difficult because unclear boundaries and structural decay obscure coupling issues. A systematic architecture review exposes these shallow modules and poor test seams to create a clear improvement strategy.