Use Case: Review & Quality

Scenario 1: Pre-Merge Review

Profile: Senior Developer, reviewing code before creating a PR

Step 1: General review

“Is this code ready to merge?”

Tool: /code-review (command) invokes code-reviewer agent (Sonnet)

Input	Uncommitted code changes (git diff)
Output	Review report: security issues, code quality, patterns. Only flags issues with >80% confidence. Verdict: approve/needs-changes

Step 2: Language-specific review

“Check the Python code specifically for type hints and Pythonic patterns.”

Tool: python-reviewer agent (Sonnet) - invoke directly or via /python-review

Input	Python code changes
Output	Python-focused review: security (bandit), types (mypy), style (ruff), PEP 8 compliance

Step 3: Security-focused review

“This touches authentication - check it for vulnerabilities.”

Tool: security-reviewer agent

Input	Code with security-sensitive changes (auth, input handling, crypto)
Output	Security analysis: OWASP top 10, injection, auth bypasses, secrets, dependencies

---

Scenario 2: TypeScript PR Review

Profile: Senior Developer, reviewing a teammate’s TypeScript PR

Step 1: TypeScript-specific review

“Review this TypeScript PR for type safety and async correctness.”

Tool: typescript-reviewer agent (Sonnet)

Input	TypeScript/JavaScript code changes
Output	TS review: any usage, non-null assertions, unhandled promises, React dependency arrays, XSS vectors

---

Review Tool Comparison

Tool	Focus	Best for	Model
/code-review	General quality + security	First-pass review of any language	Sonnet
python-reviewer	Python idioms, types, security	Python-specific deep review	Sonnet
typescript-reviewer	TS type safety, async, React	TypeScript/JavaScript deep review	Sonnet
security-reviewer	Vulnerabilities only	Security-sensitive changes	Opus

Recommended flow: Start with /code-review for a general pass, then follow up with a language-specific reviewer if needed. Use security-reviewer for auth, payment, or input-handling changes.