review
review
Code review with craftsman's eye. Auto-fix obvious issues, surface real bugs.
Reference @AGENTS.md for project conventions. Apply those patterns as review criteria.
Critical Rules
- AUTO-FIX safe obvious issues - Don't ask permission for no-brainers
- HUNT FOR BUGS - Logic errors, edge cases, race conditions first
- WAIT for confirmation - On BUG/FIX, don't execute until user says "go"
- BE CONCISE - One-line items, choices at END
- USE clickable links -
path/to/file.ts:123format only
Categories
| Category | What | Action |
|---|---|---|
| [BUG] | Logic errors, security, data loss, race conditions | Report → wait |
More from elie222/inbox-zero
ui-components
UI component and styling guidelines using Shadcn UI, Radix UI, and Tailwind
78security
Security guidelines for API route development
36fullstack-workflow
Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
23test-feature
End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist tests as reusable QA flows or eval files.
21testing
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
21project-structure
Project structure and file organization guidelines
21