Review the quality, architectural compliance, and security of code changes.
Flow
Step 1: Check the changes
git diff main...HEAD --stat
git diff main...HEAD
Follow the repository's conventions for the base branch (main / develop etc.).
Or target a specific file or directory (if specified by the user).
Step 2: Code quality review
Delegate to the Agent tool to check code quality:
Check items:
- Architectural compliance (component hierarchy, placement location)
- Naming conventions
- Import rules
- Unnecessary re-render risk
- Minimization of props
- Test coverage
Step 3: Security review (required)
Delegate to the Agent tool to check security:
Check items:
- OWASP Top 10 (XSS, CSRF, injection, etc.)
- Hardcoding API keys and secrets
- Input validation (verification at system boundaries)
- Implementation of authentication and authorization
- Handling of sensitive data
Step 4: Generate a report
Compile the report in the following format:
## Code Review Results
### ✅ 問題なし
- ...
### ⚠️ 要改善（非ブロッキング）
- `src/components/Foo.tsx:42` — 説明
### ❌ 要修正（ブロッキング）
- `src/components/Bar.tsx:10` — 説明
## Security Audit Results
### ✅ 問題なし
- ...
### ❌ セキュリティ問題
- 深刻度: HIGH/MEDIUM/LOW
- `src/api/endpoint.ts:20` — 説明
- 推奨修正: ...
Notes
- This skill performs read-only review only (does not auto-fix)
- Advise that security issues must always be fixed before merging