litestar-fullstack-inertia: Command for Claude Code

Review Workflow

You are reviewing the feature: $ARGUMENTS

Review Objectives

1. Quality Gate Verification: All checks must pass
2. Pattern Extraction: Document new patterns for future use
3. Documentation Update: Ensure patterns library is updated
4. Final Approval: Ready for commit/merge

---

Checkpoint 0: Load Review Context

Load feature context:

cat specs/active/{slug}/prd.md
cat specs/active/{slug}/tasks.md
cat specs/active/{slug}/tmp/new-patterns.md 2>/dev/null

Identify modified files:

git diff --name-only HEAD~5 | head -20
# or
git status --short

Output: "✓ Checkpoint 0 complete - [N] files to review"

---

Checkpoint 1: Quality Gate - Tests

Run full test suite:

make test

Expected: All tests pass

If failures: Stop and fix before continuing.

Output: "✓ Checkpoint 1 complete - All tests pass"

---

Checkpoint 2: Quality Gate - Linting

Run pre-commit hooks:

make pre-commit

Run type checking:

make type-check

Run slots check:

make slotscheck

Run frontend linting:

npx biome check resources/

Expected: All linting passes with zero errors

Output: "✓ Checkpoint 2 complete - All linting passes"

---

Checkpoint 3: Quality Gate - Coverage

Run coverage analysis:

make coverage

Check coverage for modified modules:

uv run pytest tests/ --cov=app/domain/{feature} --cov-report=term-missing

Required: 90%+ coverage on new/modified code

Output: "✓ Checkpoint 3 complete - Coverage: [N]%"

---

Checkpoint 4: Code Quality Analysis

Use analyze tool for comprehensive review:

mcp__pal__analyze(
    step="Reviewing code quality for {slug}...",
    step_number=1,
    total_steps=2,
    next_step_required=true,
    findings="...",
    analysis_type="quality",
    relevant_files=["app/domain/{feature}/..."]
)

Check for:

1. Anti-patterns from quality-gates.yaml
2. Type hint consistency (PEP 604 style)
3. Docstring coverage
4. Error handling patterns
5. Security considerations