---

name: review-changes description: Review uncommitted code changes against project standards. Similar to /review-code but scoped to changed files only. Suggests fixes and in auto-edit mode fixes automatically.

Review Changes Skill

Reviews uncommitted code changes against project standards. Focused review of only modified files.

Invocation

• /review-changes - Review all uncommitted changes
• /review-changes --fix - Review and auto-fix issues
• /review-changes --staged - Review only staged changes
• /review-changes --check - Dry run, report only

Flags

• --check - Report issues without making changes
• --fix - Auto-fix all issues
• --staged - Only review staged files (git add)
• --focus=[area] - Focus on: types, css, unused, lint

Workflow

Copyflowchart TD
    A[User Request] --> B[Get Changed Files]
    B --> C[Categorize Changes]
    C --> D[Review Code Changes]
    D --> E[Review Content Changes]
    E --> F[Apply Fixes]
    F --> G[Validate]
    G --> H[Generate Report]

Phase 1: Get Changed Files

Detect Changes

Copy# All uncommitted changes
git status --porcelain

# Staged only
git diff --cached --name-only

# Unstaged only
git diff --name-only

File Categories

Phase 2: Review Code Changes

For each changed code file, apply relevant checks from /review-code:

Type Safety

• No new any types
• Explicit return types
• Null handling
• Import type syntax

Code Quality

• No unused variables/imports
• Edge cases handled
• Error handling present
• Self-explanatory names

CSS (if applicable)

• Semantic class names
• Tailwind values only
• CSS variables for theme

Astro Components

• Proper structure order
• Props typed
• Accessibility considered

Phase 3: Review Content Changes

For changed .md files in content/, apply /review-posts checks:

Structure

• Title (H1) present
• TLDR comprehensive
• No manual ToC
• References section

Code Blocks

• Boilerplate collapsed
• Proper language specified
• Title attribute for context

Quality

• Concise writing
• No filler content
• Inline references

Phase 4: Focus Areas

--focus=types

Only check:

• Type annotations
• import type usage
• Null handling
• Return types

--focus=css

Only check:

• Inline Tailwind vs classes
• CSS variable usage
• Tailwind value compliance

--focus=unused

Only check:

• Unused imports
• Unused variables
• Unused functions

--focus=lint

Only run:

Copynpm run lint -- [changed-files]
npm run format -- --check [changed-files]

Phase 5: Apply Fixes

With --fix

1. Apply auto-fixable issues
2. Report manual fixes needed
3. Run validation

Without --fix

1. Report all issues
2. Categorize by severity
3. Suggest fix commands

Phase 6: Validate Changes

After fixes:

Copynpm run check     # TypeScript
npm run lint      # ESLint
npm run build     # Build

Phase 7: Generate Report

Copy# Changes Review Report

## Files Changed

- Code files: [count]
- Content files: [count]
- Style files: [count]

## Issues Found

### Critical (Must Fix)

- [ ] [File]: [Issue]

### Warnings

- [ ] [File]: [Issue]

### Suggestions

- [ ] [File]: [Suggestion]

## Fixes Applied (with --fix)

- [Fix 1]
- [Fix 2]

## Manual Fixes Needed

- [File]: [What to fix]

## Validation

- TypeScript: PASS/FAIL
- ESLint: PASS/FAIL
- Build: PASS/FAIL

Common Issues by File Type

TypeScript Files

Astro Files

CSS Files

Markdown Files

Integration with Git Hooks

This skill can be run as a pre-commit check:

Copy# In .husky/pre-commit
/review-changes --staged --check

Quick Commands

Copy# Quick lint check on changes
npm run lint -- $(git diff --name-only -- '*.ts' '*.astro')

# Type check
npm run check

# Format check
npm run format -- --check $(git diff --name-only)

Reference Documents

IMPORTANT: Before reviewing changes, read these documents from the project root:

Usage: Use the Read tool with absolute paths (e.g., /path/to/project/llm_docs/code-standards.md) to read these files before starting work.

Tools Available

• Bash - Git commands, npm scripts
• Read - Read changed files
• Edit - Apply fixes
• Glob - Find related files
• Grep - Search patterns