code-architecture-review — Claude Code skill: architecture review
code-architecture-review evaluates codebase structure for module dependencies and coupling. Catches architectural problems before they turn into debt.
Apache-2.0 270 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a claude-codeWhat code-architecture-review does
The skill analyzes how modules depend on each other and how easy it will be to change them. It relies on three reference files: patterns.md dictates creation patterns, sharp_edges.md lists critical failures and their causes, validations.md sets validation rules.
The philosophy is built on dependencies pointing toward stability, each module changing for one reason, and if a component cannot be tested in isolation, it is too coupled. Abstractions are discovered, not invented upfront.
Fits pull request reviews with structural changes, new feature architecture assessment, refactoring planning, and pre-release audits.
What it helps with
- check module dependencies in a codebase
- assess feature architecture before merging
- find excessive coupling between components
- plan refactoring based on structural issues
- audit architecture before a release
Example prompts for the agent
- Check the architecture of
src/ordersfor coupling - Assess dependencies in pull request #342
- Find modules with multiple reasons to change
How to install code-architecture-review
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a claude-code2Manually: put the files in place
~/.claude/skills/code-architecture-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-architecture-review/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a codex2Manually: put the files in place
.agents/skills/code-architecture-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a cursor2Manually: put the files in place
.cursor/skills/code-architecture-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/code-architecture-review2Manually: put the files in place
.github/skills/code-architecture-review/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/code-architecture-reviewManually: put the files in place
.devin/skills/code-architecture-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-architecture-review
How to install code-architecture-review in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill code-architecture-review -a claude-code, then open ~/.claude/skills/code-architecture-review/SKILL.md.
What does code-architecture-review do?
Checks code structure for module dependencies, component coupling, and pattern compliance using built-in reference files. Catches architectural problems while they are still cheap to fix.
Which reference files does the skill use?
patterns.md with creation patterns, sharp_edges.md with critical failure causes, and validations.md with validation rules. The skill relies on them during review and corrects the user if a request conflicts with the references.
Source text
SKILL.md · Apache-2.0
--- name: code-architecture-review description: Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned. --- # 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.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity