Code Architecture Review

This one's for catching the structural problems that make your codebase progressively harder to change. It reviews architecture through the lens of dependencies and coupling, asking whether modules can be tested in isolation and whether they have single, clear responsibilities. Use it when evaluating PRs with structural changes, planning refactors, or before releases when tech debt has piled up. The philosophy here is pragmatic: good architecture is invisible, bad architecture is a constant tax. It comes with reference files for patterns, known sharp edges, and validation rules, so you're getting specific guidance rather than generic best practices. Honest take: most teams wait too long to do this kind of review, and by then the fixes are 10x more expensive.

skills.sh installs: 270
GitHub stars: 202
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add omer-metin/skills-for-antigravity --skill code-architecture-review --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub