Review Architecture

Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared mechanisms (structural boundaries, data ownership, NFR mechanisms, failure isolation, state consistency, evolution/versioning, domain binding) plus decision soundness, reversibility, and provenance (self-certification of reverse-engineered claims). Use after an ADR, architecture doc, domai

155 stars 30 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add serpro69/claude-toolbox

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add serpro69/claude-toolbox --skill review-architecture
Manual install
git clone --depth 1 https://github.com/serpro69/claude-toolbox.git /tmp/claude-toolbox
mkdir -p ~/.claude/skills
cp -r /tmp/claude-toolbox/klaude-plugin/skills/review-architecture ~/.claude/skills/review-architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Architecture Review

## Overview

Review a single committed architecture artifact against the system it describes. The review is **claim-driven**: the artifact is normalized into an explicit, inspectable claim-set (Pass 0), each claim is verified for the existence and topology of the mechanism it names (Pass 1), and the artifact's decisions are graded against its own stated context (Pass 2). Verification is delegated to the read-only `architecture-reviewer` agent; this skill owns acceptance and presentation.

**The altitude line — the load-bearing constraint.** This skill verifies that declared mechanisms *exist* and are wired into the right *topology* — "is there an idempotency-key column / a circuit breaker targeting dependency D / a `/v2/` route." It never verifies behavioral correctness ("does the code *use* the key correctly under retries") — that belongs to `/kk:review-code` and `/kk:review-spec`. Every dimension, the input contract, and the eval strategy are consequences of this line. Do not let a dimension expand into whole-system behavioral reasoning.

**Security architecture is delegated OUT** to the PAL `secaudit` tool (`mcp__pal__secaudit`). There is no `kk:` security skill. Trust boundaries, authN/authZ enforcement, and data-classification flow drag the reviewer into runtime analysis — surface such claims under Not Reviewed with a `secaudit` pointer (see [output-contract.md](output-contract.md)).

## Conventions
Read the full skill on GitHub

Details

Skill name
review-architecture
Path
klaude-plugin/skills/review-architecture/SKILL.md
License
Apache-2.0
Repo updated
18 November 2026

FAQ

What does the Review Architecture skill do?

Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared mechanisms (structural boundaries, data ownership, NFR mechanisms, failure isolation, state consistency, evolution/versioning, domain binding) plus decision soundness, reversibility, and provenance (self-certification of reverse-engineered claims). Use after an ADR, architecture doc, domai

How do I install the Review Architecture skill?

Claude Code plugin: /plugin marketplace add serpro69/claude-toolbox. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Review Architecture popular?

It lives in serpro69/claude-toolbox, which has 155 GitHub stars and 30 forks, and is included in 1 curated skill list.

Related skills

Brainstorm

155

serpro69/claude-toolbox

TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to /kk:design; durable domain glossary/reference kits to /kk:model; implementation and fixes to /kk:implement. Not for nontechnical brainstorming.

Productivity & NotesIn 1 list30

Chain of Verification

155

serpro69/claude-toolbox

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

AI, LLMs & AgentsIn 1 list30

Clarify Docs

155

serpro69/claude-toolbox

TRIGGER when: asked to clarify or improve existing documentation, PR drafts or issue descriptions, including URLs and pasted bodies. Saves results locally, grounded in requirements and source while preserving meaning. Not for requests to implement, fix or work on an issue, code, config, generic response brevity, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or invoking implementation.

Writing & ContentIn 1 list30

Review Code

155

serpro69/claude-toolbox

Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.

Software DevelopmentIn 1 list30

Patent Software Ip

188

jaccen/Awesome-Gaussian-Skills

Generate CN patent docs (claims, specification, abstract) and software copyright materials from AI/big-data project code or docs. Covers 7 AI domains + big data, 11 claim templates, auto domain detection, desensitization, prior-art search, and self-check. Use when: drafting CN patents from AI code/docs, generating software copyright materials, prior-art search for AI inventions, 专利撰写/软件著作权/AI知识产权/脱敏处理.

Software Development13

Debug

116

SeifBenayed/cloclo

Troubleshoot and debug issues. Use when the user reports an error, a test failure, unexpected behavior, or asks to investigate why something isn't working.

Software DevelopmentIn 1 list32

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.