skills.rest
jshsakura
jshsakuraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architect-reviewer

Identify architectural boundaries, coupling risks, and maintainability issues in codebases.

22|2|Updated Mar 24, 2026
Search Tags:#architecture#maintainability#risk-assessment#coupling#code-review#boundaries#system-design
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill architect-reviewer-jshsakura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-reviewer
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/architect-reviewer
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill architect-reviewer-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural reviews to surface coupling, boundaries, and maintainability risks early in the delivery lifecycle.

Core Features & Use Cases

  • Evidence-based assessment of system boundaries, module dependencies, data ownership, and contract stability.
  • Actionable recommendations with minimal, high-impact changes and clear rollout considerations.
  • Use Case: When a new service or module is added, the reviewer provides a risk-adjusted target architecture and migration plan.

Quick Start

Provide an architecture review outline for the new payment service integration.

Frequently Asked Questions about architect-reviewer

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

FAQPage Schema
How do I identify architecture boundaries and coupling risks in my codebase?▼

Architecture boundaries and coupling risks are identified through evidence-driven assessment of module dependencies and contract stability, producing concrete recommendations with minimal, high-impact changes to reduce long-term maintainability issues.

What is an evidence-driven architecture review?▼

An evidence-driven architecture review surfaces coupling, boundaries, and maintainability risks early in the delivery lifecycle by assessing system boundaries, module dependencies, data ownership, and contract stability.

How do I assess maintainability risks when adding a new service or module?▼

Maintainability risks for a new service or module are assessed by evaluating data ownership and contract stability, yielding a risk-adjusted target architecture and migration plan with clear rollout considerations.

Does an architecture review include backward compatibility and rollout considerations?▼

Architecture reviews include backward compatibility and rollout considerations by providing actionable recommendations with minimal, high-impact changes and validation steps to ensure safe migration.

Can I generate a migration plan for a new payment service integration?▼

You can generate a migration plan for a new payment service integration by providing an architecture review outline, which produces a risk-adjusted target architecture and actionable rollout considerations.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
MartyBonacciMartyBonacci
65

specswarm-modify

Modify feature behavior with impact analysis and backward-compatibility assessment.

Community
Advanced
leogallegoleogallego
1

kotlin-project-code-review

Identify architectural drift and maintainability risks in Kotlin Multiplatform code reviews.

Community
Advanced
Destynova2Destynova2
5

cli-audit-tangle

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

Community
Advanced