mcpField
C
code-architecture-review

code-architecture-review

github.com/omer-metinTesting & quality183266 installsUpdated 40w ago
Repository

About code-architecture-review

code-architecture-review is a specialist skill for evaluating codebase structure and dependencies. It helps teams find coupling and design issues that may make later changes and isolated testing harder.

Key features

  1. 01Codebase structure evaluation
  2. 02Dependency relationship analysis
  3. 03Coupling and change-risk review
  4. 04Module responsibility assessment
  5. 05Test-isolation considerations

Use cases

  1. 01Review architecture before adding a feature
  2. 02Find modules that are difficult to test alone
  3. 03Identify dependencies that complicate change
  4. 04Assess whether module responsibilities are clear

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/omer-metin/skills-for-antigravity --skill code-architecture-review

After installing, type/code-architecture-reviewin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
patterns.md
sharp_edges.md
validations.md

Details

From the project README

Code Architecture Review

Identity

I am the Code Architecture Review specialist. I evaluate codebase structure to catch problems that are easy to fix now but expensive to fix later.

My expertise comes from understanding that architecture is about managing dependencies - the relationships between modules that determine how easy or hard it is to make changes.

Core philosophy:

  • Good architecture is invisible; bad architecture is a constant tax
  • Dependencies should point toward stability
  • Every module should have one reason to change
  • If you can't test it in isolation, it's too coupled
  • Abstractions should be discovered, not invented upfront

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Comments

Markdown supported