New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Architecture Review

by athola in athola/claude-night-market

Assesses architecture decisions, ADR compliance, and coupling.

MITAuto-check passedDevelopment

Install Architecture Review

skills CLI
$ npx skills add athola/claude-night-market --skill architecture-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install athola/claude-night-market architecture-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/pensive/skills/architecture-review .claude/skills/architecture-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architecture-review
GitHub stars
341
Token cost
~2.1k tokens
SKILL.md length
801 words
Files
6
Skills in repo
152
Repo updated
First seen
Licence
MIT

At a glance

Assesses architecture decisions, ADR compliance, and coupling.

  • Works in 7 steps: Establish Context… → ADR Audit (arch-review:adr-audit) → Interaction Mapping… → …
  • Evaluating design changes
  • SKILL.md covers Testing, Quick Start, When To Use and When NOT To Use, plus 5 more sections
  • Calls git, rg and pytest

What it does

Architecture Review is an agent skill from athola/claude-night-market. Assesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `modules/adr-audit.md`, `modules/ceremony-audit.md` and `modules/coupling-analysis.md`).

It sits in Development, covering Architecture decision records and Software architecture. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.

When your agent uses it

  • Evaluating design changes
  • Validating structural decisions before merging

Example prompts

  • “Use the architecture-review skill to assess architecture decisions, ADR compliance, and coupling”
  • “/architecture-review”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Establish Context (arch-review:context-established)
  2. ADR Audit (arch-review:adr-audit)
  3. Interaction Mapping (arch-review:interaction-mapping)
  4. 5: Invariant Conflict Detection (arch-review:invariant-check)
  5. Principle Checks (arch-review:principle-checks)
  6. 5: Ceremony Audit (arch-review:ceremony-audit)
  7. Risks and Actions (arch-review:risks-actions)

What it can do on your machine

Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • rg
    • pytest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architecture Review loads about 2.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 801 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 801 words, ~2,139 tokens.

Download SKILL.mdSave it as .claude/skills/architecture-review/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
architecture-review
description
Assesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.
alwaysApply
false
category
architecture
tags
architecture, design, adr, coupling, patterns, principles
usage_patterns
architecture-assessment, adr-audit, refactor-review, design-validation
complexity
advanced
model_hint
deep
estimated_tokens
300
progressive_loading
true
dependencies
imbue:proof-of-work, imbue:diff-analysis/modules/risk-assessment-framework, imbue:review-core, imbue:structured-output
modules
modules/adr-audit.md, modules/coupling-analysis.md, modules/principle-checks.md, modules/fpf-methodology.md, modules/ceremony-audit.md

Testing

Run pytest plugins/pensive/tests/skills/test_architecture_review.py to verify review logic.

Architecture Review Workflow

Architecture assessment against ADRs and design principles.

Quick Start

bash
/architecture-review

When To Use

  • Approving reimplementations.
  • Large-scale refactoring reviews.
  • System design changes.
  • New module/service introduction.
  • Dependency restructuring.

When NOT To Use

  • Selecting architecture paradigms - use archetypes skills
  • API surface review - use api-review
  • Selecting architecture paradigms - use archetypes skills
  • API surface review - use api-review

Progressive Loading

Load modules based on review scope:

  • modules/adr-audit.md (~400 tokens): ADR verification and documentation.
  • modules/coupling-analysis.md (~450 tokens): Dependency analysis and boundary violations.
  • modules/principle-checks.md (~500 tokens): Code quality, security, and performance.
  • modules/fpf-methodology.md (~800 tokens): FPF (Functional, Practical, Foundation) multi-perspective review methodology.
  • modules/ceremony-audit.md (~600 tokens): Manual lenses for mapping layers that never diverge. Passthrough mappers, twin types, speculative DTOs, single-implementation interfaces. Includes the IO boundary counter-signal.

Load all modules for full reviews. For focused reviews, load only relevant modules.

Required TodoWrite Items

  1. arch-review:context-established: Repository, branch, motivation.
  2. arch-review:adr-audit: ADR verification and new ADR needs.
  3. arch-review:interaction-mapping: Module coupling analysis.
  4. arch-review:invariant-check: Invariant conflict detection and 3-option analysis.
  5. arch-review:principle-checks: LoD, security, performance.
  6. arch-review:ceremony-audit: Mapping layers that never diverge.
  7. arch-review:risks-actions: Recommendation and follow-ups.
  8. arch-review:findings-verified

Workflow

Step 1: Establish Context (arch-review:context-established)

Confirm repository and branch:

bash
pwd
git status -sb

Document:

  • Feature/bug/epic motivating review.
  • Affected subsystems.
  • Architectural intent from README/docs.
  • Design trade-off assumptions.
Step 2: ADR Audit (arch-review:adr-audit)

Load: modules/adr-audit.md

  • Locate ADRs in project.
  • Verify required sections.
  • Check status flow.
  • Confirm immutability compliance.
  • Flag need for new ADRs.
Step 3: Interaction Mapping (arch-review:interaction-mapping)

Load: modules/coupling-analysis.md

  • Diagram before/after module interactions.
  • Verify composition boundaries.
  • Check data ownership clarity.
  • Validate dependency flow direction.
  • Identify coupling violations.
Step 3.5: Invariant Conflict Detection (arch-review:invariant-check)

Before checking principles, identify whether the changes conflict with existing design invariants. This is the highest-judgment step in architecture review: models get this wrong more often than any other call.

Identify existing invariants:

  1. Scan ADRs for recorded decisions still in "accepted" status
  2. Check module boundaries (are imports crossing layers that previously didn't?)
  3. Check data flow direction (does data now flow in a new direction?)
  4. Check API contracts (are public interfaces changing shape?)
  5. Check structural patterns (is a new pattern being introduced alongside an existing one?)
bash
# Detect boundary crossings in changed files
git diff --name-only | while read f; do
  head -20 "$f" 2>/dev/null | rg "^(import|from|use |require)" || true
done

When a conflict is detected:

Do NOT recommend a resolution. Present the three options and escalate to human judgment:

OptionWhen RightWhen Wrong
Preserve invariant (reject feature)Invariant simplifies many things; feature is marginalFeature is genuinely needed and invariant is stale
Layer on top (add inelegantly)Feature is needed; invariant still valuable; imperfection is OKLayering creates a maintenance trap that will compound
Revise invariant (change the design)Genuine new learning invalidates the original reasoningYou're "cleaning up" a decision you don't fully understand

Output format:

markdown
### Invariant Conflicts

[I1] **[Invariant name]** — [what decision it represents]
- **Location**: file.py:42
- **Anchor**: `verbatim source text at line 42`
- **Conflict**: [what change clashes]
- **Options**: Preserve / Layer / Revise
- **Recommendation**: ESCALATE TO HUMAN
- **Risk if wrong**: [what compounds]

Why this matters: Bad invariant decisions compound. After a few wrong calls the codebase becomes unsalvageable. This is a judgment problem rather than a context problem: the agent should surface it, not solve it.

Show full SKILL.md (322 more words)Show less
Step 4: Principle Checks (arch-review:principle-checks)

Load: modules/principle-checks.md

  • Law of Demeter.
  • Anti-slop patterns.
  • Security (input validation, least privilege).
  • Performance (N+1 queries, caching).
Step 4.5: Ceremony Audit (arch-review:ceremony-audit)

Load: modules/ceremony-audit.md

Coupling analysis (Step 3) finds boundaries that leak. This step finds the opposite failure: boundaries that cost something and separate nothing.

  • Passthrough mappers whose fields are all 1:1 copies.
  • Twin types that are structurally identical across layers.
  • Speculative DTOs with no external contract pinning their shape.
  • Interfaces with exactly one implementation and no test double.

Each finding must name the need the ceremony serves today. If no current need can be named, the ceremony is the finding.

Do not flag mappers at an IO boundary. They are load-bearing even when they look like passthroughs, because they stop future internal fields from escaping. See the counter-signal in the module.

Step 5: Risks and Actions (arch-review:risks-actions)

Summarize using imbue:diff-analysis/modules/risk-assessment-framework:

  • Current vs proposed architecture.
  • Business impact.
  • Technical debt implications.

List follow-ups with owners and dates.

Provide recommendation:

  • Approve: Architecture sound.
  • Approve with actions: Minor issues to address.
  • Block: Fundamental problems requiring redesign.

Architecture Principles Checklist

Coupling
  • Dependencies follow defined boundaries.
  • No circular dependencies.
  • Extension points used properly.
  • Abstractions don't leak.
Cohesion
  • Related functionality grouped.
  • Single responsibility per module.
  • Clear module purposes.
Layering
  • Layers have clear responsibilities.
  • Dependencies flow downward.
  • No layer bypassing.
Invariants
  • Existing design invariants identified.
  • Conflicts between changes and invariants surfaced.
  • Three-option analysis (preserve/layer/revise) presented.
  • Invariant changes escalated to human judgment.
  • No silent invariant revisions in the diff.
Evolution
  • Changes are reversible.
  • Migration paths are clear.
  • ADRs document decisions.
Verify Findings Are Grounded (arch-review:findings-verified)

Write findings to .review/findings.json, run the citation verifier (Skill(imbue:review-core) Step 5), and drop or label UNVERIFIED any the verifier rejects.

Exit Criteria

  • Context established, ADR audit complete, interaction mapping done, invariant conflicts surfaced, principle checks run, risks and actions documented.
  • Every reported finding carries a Location + verbatim Anchor confirmed by citation_verifier.py (exit 0), or unverified findings were dropped or labeled UNVERIFIED.

© athola, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in plugins/pensive/skills/architecture-review of athola/claude-night-market.

  • SKILL.md
  • modules/adr-audit.md
  • modules/ceremony-audit.md
  • modules/coupling-analysis.md
  • modules/fpf-methodology.md
  • modules/principle-checks.md

Open the folder on GitHubat commit 9f3eb00

Compare with similar skills

Architecture Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architecture Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architecture Review this skillathola/claude-night-market341—~2.1kAutomated safety check: PassMIT
Create Vibe Featuremistralai/mistral-vibe5.1k—~1.4kAutomated safety check: PassApache-2.0
Architecture Decisions and ADRsfirst-fluke/oh-my-agent1.3k—~2.6kAutomated safety check: PassMIT
System Architecture DesignerJeffallan/claude-skills12k—~1.2kAutomated safety check: PassMIT
Light System DesignLight0305/Light-skills640—~3.6kAutomated safety check: PassMIT
Architecture DesignerAratKruglik/claude-laravel1551 repos~895Automated safety check: PassNone

Similar skills

  • Create Vibe Feature

    mistralai/mistral-vibe

    Official

    Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.

    5.1k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Architecture Decisions and ADRs

    first-fluke/oh-my-agent

    Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.

    1.3k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • System Architecture Designer

    Jeffallan/claude-skills

    Guides system architecture design end to end: gathering requirements, matching them to a pattern, documenting trade-offs with ADRs, and reviewing.

    12k GitHub stars~1.2k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Light System Design

    Light0305/Light-skills

    Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.

    640 GitHub stars~3.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Architecture Designer

    AratKruglik/claude-laravel

    A skill your agent uses when designing new system architecture, reviewing existing designs, or making architectural decisions.

    155 GitHub starsUsed in 1 repo~895 tokens
    DevelopmentAuto-check passed

  • Architecture Decision Record Writer

    dralgorhythm/claude-agentic-framework

    Writes Architecture Decision Records with title, status, context, decision, rationale and consequences for significant technical choices, kept short and numbered.

    125 GitHub stars~529 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from athola/claude-night-market

All 152 skills in this repo

  • Night Market Diagnostics Toolkit

    athola/claude-night-market

    Run and interpret repo diagnostic scripts (ratchets, validators, token stats).

    341 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Skills Eval

    athola/claude-night-market

    Evaluate Claude skill quality through auditing. An agent skill from athola/claude-night-market.

    341 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Agent Teams

    athola/claude-night-market

    Coordinates Claude agent teams via filesystem protocol. An agent skill from athola/claude-night-market.

    341 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Delegation Core

    athola/claude-night-market

    Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer).

    341 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Elegant Code

    athola/claude-night-market

    Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage.

    341 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Skill Library Mission

    athola/claude-night-market

    Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review.

    341 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Architecture Review

What does Architecture Review do?

Assesses architecture decisions, ADR compliance, and coupling. Architecture Review is an agent skill from athola/claude-night-market. Assesses architecture decisions, ADR compliance, and coupling.

When should I use Architecture Review?

Architecture Review fits situations like: evaluating design changes; validating structural decisions before merging.

How do I install Architecture Review in Claude Code?

Run `npx skills add athola/claude-night-market --skill architecture-review -a claude-code`. Or copy the skill folder (plugins/pensive/skills/architecture-review in athola/claude-night-market) into .claude/skills/architecture-review in your project. Claude Code loads it when a task matches its description.

How do I install Architecture Review in Codex?

Run `npx skills add athola/claude-night-market --skill architecture-review -a codex`. Or copy the skill folder (plugins/pensive/skills/architecture-review in athola/claude-night-market) into .agents/skills/architecture-review in your project. Codex loads it when a task matches its description.

Can I use Architecture Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill architecture-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-review, .gemini/skills/architecture-review, .github/skills/architecture-review and .opencode/skills/architecture-review in your project.

What does Architecture Review need to run?

Going by SKILL.md and its folder, Architecture Review needs the command-line tools its instructions call (git, rg and pytest).

Does Architecture Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Architecture Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architecture Review use?

Architecture Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architecture Review use?

About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architecture Review?

Skills that share tags, products or a category with Architecture Review: Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars), Architecture Decisions and ADRs (first-fluke/oh-my-agent, 1.3k stars), System Architecture Designer (Jeffallan/claude-skills, 12k stars) and Light System Design (Light0305/Light-skills, 640 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architecture Review?

athola (a GitHub user) maintains it in athola/claude-night-market, which has 341 GitHub stars. The repository holds 152 skills in this directory. The repository was last updated on October 9, 2026.

Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.