/architecture-review
Principal-level architecture assessment against ADRs and design patterns.
$ npx -y skills add athola/claude-night-market --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/architecture-review
Context preview
What this command does when you run it.
Principal-level architecture assessment against ADRs and design patterns.
Command definition
architecture-review.mdArchitecture Review Command
Principal-level architecture assessment against ADRs and design patterns.
Usage
/architecture-review
What It Does
1. **Context**: Establish review scope 2. **ADR Audit**: Check architecture decisions 3. **Interaction Mapping**: Diagram dependencies 4. **Principle Checks**: Validate design patterns 5. **Risk Assessment**: Document consequences
Scope
- Module boundaries
- Dependency graphs
- Data flow patterns
- Coupling analysis
- ADR compliance
War Room Checkpoint (Automatic)
**Purpose**: Assess whether architecture findings warrant expert deliberation before recommendation.
**Auto-triggers when** (moderate approach):
- ADR violations without clear remediation path, OR
- High coupling score (>0.7), OR
- Multiple module boundary violations (>2), OR
- Conflicting design principles detected
**Checkpoint invocation** (automatic, after Risk Assessment):
Skill(attune:war-room-checkpoint) with context:
source_command: "architecture-review"
decision_needed: "Architecture recommendation for [component/PR]"
blocking_items: [
{type: "adr", description: "Violates ADR-003 without justification"},
{type: "coupling", description: "High coupling between auth and payment"}
]
files_affected: [modules under review]
profile: [from user settings, default: "default"]**War Room Questions** (when escalated):
- "Should we recommend blocking or propose remediation?"
- "Does this coupling warrant refactoring or is it acceptable?"
- "Should a new ADR be created to document this deviation?"
**Response handling**:
| RS Score | Mode | Action | |----------|------|--------| | RS <= 0.40 | Express | Quick recommendation, continue | | RS 0.41-0.60 | Lightweight | Panel reviews trade-offs | | RS > 0.60 | Full Council | Full deliberation on architecture decision |
**Skip conditions**:
- All ADRs compliant
- Coupling within acceptable thresholds
- No boundary violations
Output
- Architecture assessment
- ADR compliance status
- Coupling violations
- Principle adherence
- Recommendations (Approve/Block)
- War Room session ID (if escalated)
Read more
Architecture Review Command
Principal-level architecture assessment against ADRs and design patterns.
Usage
/architecture-review
What It Does
1. **Context**: Establish review scope 2. **ADR Audit**: Check architecture decisions 3. **Interaction Mapping**: Diagram dependencies 4. **Principle Checks**: Validate design patterns 5. **Risk Assessment**: Document consequences
Scope
- Module boundaries
- Dependency graphs
- Data flow patterns
- Coupling analysis
- ADR compliance
War Room Checkpoint (Automatic)
**Purpose**: Assess whether architecture findings warrant expert deliberation before recommendation.
**Auto-triggers when** (moderate approach):
- ADR violations without clear remediation path, OR
- High coupling score (>0.7), OR
- Multiple module boundary violations (>2), OR
- Conflicting design principles detected
**Checkpoint invocation** (automatic, after Risk Assessment):
Skill(attune:war-room-checkpoint) with context:
source_command: "architecture-review"
decision_needed: "Architecture recommendation for [component/PR]"
blocking_items: [
{type: "adr", description: "Violates ADR-003 without justification"},
{type: "coupling", description: "High coupling between auth and payment"}
]
files_affected: [modules under review]
profile: [from user settings, default: "default"]**War Room Questions** (when escalated):
- "Should we recommend blocking or propose remediation?"
- "Does this coupling warrant refactoring or is it acceptable?"
- "Should a new ADR be created to document this deviation?"
**Response handling**:
| RS Score | Mode | Action | |----------|------|--------| | RS <= 0.40 | Express | Quick recommendation, continue | | RS 0.41-0.60 | Lightweight | Panel reviews trade-offs | | RS > 0.60 | Full Council | Full deliberation on architecture decision |
**Skip conditions**:
- All ADRs compliant
- Coupling within acceptable thresholds
- No boundary violations
Output
- Architecture assessment
- ADR compliance status
- Coupling violations
- Principle adherence
- Recommendations (Approve/Block)
- War Room session ID (if escalated)
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Other commands on claude-night-market.
- /aggregate-logs
Generate LEARNINGS.md from skill execution logs.
Open command - /analyze-skill
Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.
Open command - /bulletproof-skill
Harden skills against rationalization and bypass behaviors
Open command - /context-report
Generate context optimization report for skill directories
Open command - /create-command
Create slash commands with brainstorming and best practices
Open command - /create-hook
Create hooks with brainstorming and security-first design
Open command

