skills.rest
isymchych
isymchychCOMMUNITY
Explore all skills by this author →
GitHub

architecture-review

Evaluate architectural changes for boundary integrity and maintainability.

Updated Sep 30, 2021
Search Tags:#architecture#maintainability#refactor#risk-assessment#code-review#design-review#module-boundaries
One-click install
npx skills add https://github.com/isymchych/accel-os --skill architecture-review-isymchych
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/isymchych/accel-os/tree/main/ai/codex/skills/architecture-review
Command: npx skills add https://github.com/isymchych/accel-os --skill architecture-review-isymchych

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify and mitigate architectural risks introduced by changes, focusing on boundaries, data leakage, and long-term maintainability.

Core Features & Use Cases

  • Boundary mapping: identifies changed modules and their public interfaces, noting new dependencies and ownership shifts.
  • Leakage detection: flags repeated decisions or cross-cutting responsibilities that could cause information leakage.
  • Migration impact assessment: predicts how boundary changes ripple to callers and downstream modules, with backward-compatibility notes.

Quick Start

Provide an architecture review for the latest PR focusing on module boundaries and data flow.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I perform an architecture review for module boundaries and data leakage?▼

Architecture review evaluates module interfaces and ownership boundaries to detect data leakage. It maps changed modules, flags cross-cutting responsibilities, and produces a structured report with severity, evidence, risk, and actionable recommendations for maintainability.

What is the best way to assess migration impact on downstream callers during a refactor?▼

Migration impact assessment predicts how boundary changes ripple to downstream modules during a refactor. It generates backward-compatibility notes and identifies new dependencies, ensuring architectural shifts do not break existing callers or introduce hidden risks.

How does boundary mapping identify ownership shifts in a pull request?▼

Boundary mapping identifies changed modules and their public interfaces within a pull request. It notes new dependencies and ownership shifts, providing a clear view of how module responsibilities have migrated across the codebase.

When do I need a structured architecture findings report for a design review?▼

A structured architecture findings report is needed for design reviews affecting layering and data flow. It documents severity, evidence, and risk, helping teams mitigate long-term maintainability issues introduced by architectural changes.

Can I use this architecture review for changes affecting module interfaces and layering?▼

Yes, architecture review applies to changes affecting module interfaces, ownership boundaries, layering, and data flow. It works across pull requests, design reviews, and refactors to evaluate boundary integrity and maintainability.

What are the limitations of relying solely on code review for architectural risk assessment?▼

Standard code review often misses architectural risks like information leakage and boundary integrity. A structured architecture review explicitly maps module boundaries, detects cross-cutting responsibilities, and predicts migration impact to mitigate long-term maintainability risks.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

gitnexus-pr-review

Assess pull request changes and summarize risk and impact on execution flows.

Community
Intermediate
JordanGunnJordanGunn
6

refactor-dictionaries

Audit dictionary usage in public APIs and output a Markdown report.

Community
Intermediate
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced
SermilionSermilion
13

bill-kotlin-code-review-architecture

Analyze Kotlin module boundaries and DI scopes for architectural correctness.

Community
Advanced