Review staged files against best practices
review-stagedcommandsetup L1★0
yuriyward/electron-shadcn-ai ↗What it does
Review git staged files against project architecture and TypeScript rules
Best for
Automated gate for Electron projects when architectural boundaries (main/preload/renderer, IPC contracts, security constraints) must be enforced before commits land.
Inputs
- · Git repository with staged changes
- · AI.md file containing project rules
- · Electron + React + TypeScript codebase
Outputs
- · Priority-categorized code review findings (P0 blockers, P1 important, P2 nits)
- · File-by-file feedback with line references
- · Concrete recommendations with code snippets
Requires
- · git (for diff --staged)
- · Project AI.md rules document
Preconditions
- · Files staged in git (git add ...)
- · AI.md exists with architectural rules
- · Electron/Forge project structure in place
Failure modes
- · No staged files = no review to conduct
- · Missing AI.md = generic review only, no project-specific enforcement
- · Large staged changes make review surface area too broad
Trust signals
- · Explicitly covers Electron security (nodeIntegration, contextIsolation)
- · Enforces oRPC + Zod typed contracts for IPC
- · Cites specific file-size and concern-per-file limits