Full Code Review Skill

Runs all 7 project review skills and consolidates findings into a single report.

Usage

full-review for <component/path>

Example: full-review for deposit processor refund mechanism

Review Order

Execute each review in sequence, collecting violations:

1. Go Code Standards (golang-review)

• Code style, error handling, concurrency, contexts
• MUST: gofmt, go vet, error wrapping, context propagation
• SHOULD: small interfaces, sentinel errors, table-driven tests

2. Interface Design (go-interface)

• Interface Segregation Principle
• Consumer-defined interfaces, -er naming convention
• Accept interfaces, return concrete types

3. Testing Standards (go-testing)

• Table-driven tests, test coverage
• Race condition testing, test isolation
• Mock patterns, test helpers

4. Hexagonal Architecture (hexagonal-review)

• Port/adapter separation
• Domain isolation, dependency direction
• Infrastructure boundaries

5. Engineering Principles (engineering-review)

• SOLID principles
• Design patterns, code organization
• Dependency injection, composition

6. Logging Standards (logging-standards)

• Zap structured logging
• Log levels, field consistency
• Error context, request correlation

7. Observability Standards (observability-standards)

• Prometheus metrics
• Metric naming conventions
• Labels, histograms, counters

Output Format

Write consolidated report to ai/reviews/<component>-review-<YYYYMMDD-HHMMSS>.md

Report Structure

# Code Review: <Component>

**Date**: <timestamp>
**Reviewer**: Claude Code (full-review skill)

## Summary

| Skill | Status | MUST | SHOULD | CAN |
|-------|--------|------|--------|-----|
| golang-review | ✅/⚠️/❌ | 0 | 0 | 0 |
| go-interface | ✅/⚠️/❌ | 0 | 0 | 0 |
| ... | ... | ... | ... | ... |

**Overall**: X MUST violations, Y SHOULD violations, Z CAN suggestions

## MUST Violations (Blocking)

### [RULE-ID] Description
- **File**: path/to/file.go:line
- **Issue**: Description of the violation
- **Fix**: Recommended fix

## SHOULD Violations (Recommended)

### [RULE-ID] Description
...

## CAN Improvements (Optional)

### [RULE-ID] Description
...

## Detailed Findings by Skill

### 1. Go Code Standards
...

### 2. Interface Design
...

Execution Instructions

1. Read the target code thoroughly
2. Apply each skill's checklist systematically
3. Categorize each finding by severity (MUST/SHOULD/CAN)
4. Write the consolidated report to ai/reviews/
5. Present a brief summary to the user

Status Legend

• ✅ Pass: No violations
• ⚠️ Warning: Only SHOULD/CAN violations
• ❌ Fail: Has MUST violations