Name: review-staged
Author: yuriyward

Prompt file imported from yuriyward/fix-grammar (.claude/commands/review-staged.md). Copyright stays with the author.

Review Criteria:

Architecture & Boundaries

Main / Preload / Renderer separation: No Node/Electron APIs in renderer; keep preload as a narrow bridge.
IPC discipline: Prefer oRPC + Zod typed contracts (src/ipc/**, src/actions/**); avoid ad-hoc ipcRenderer usage.
Routing: Changes under src/routes/ should respect TanStack Router conventions; don’t hand-edit src/routeTree.gen.ts.

AI.md Rules Compliance

File size & scope: Keep files under ~300 lines; keep <=3 concerns per file; extract shared logic after 2+ uses.
Imports: Prefer @/ absolute imports; avoid barrel files/re-export index.ts patterns.
TypeScript: Keep strict types; avoid any and unsafe assertions.
Styling: Prefer Tailwind + existing UI components (src/components/ui/) over ad-hoc CSS.
Code quality: Biome formatting/lint rules (2-space indent, single quotes, organized imports).

Maintainability & Best Practices

Security (Electron):
- Avoid enabling nodeIntegration in renderer; keep contextIsolation enabled.
- Never load/execute remote code in the renderer.
- Preload should expose only minimal, explicit APIs (prefer contextBridge).
Performance: Avoid unnecessary IPC chatter; keep renderer work lightweight.
Error Handling: Clear error paths and user-facing feedback where appropriate.
Naming: Clear, descriptive variable and function names
Dependencies: Explicit dependency management, no hidden dependencies

Instructions:

Get the list of staged files: !git diff --staged --name-only
For each staged file, read its content and analyze it thoroughly
Provide structured feedback with priority levels:
- P0 (Blockers): Critical issues that violate core principles and must be fixed
- P1 (Important): Significant improvements for maintainability and consistency
- P2 (Nits): Minor suggestions and optimizations

Output Format: For each file, provide:

File path and brief summary
Priority-categorized issues with specific line references
Concrete recommendations with code snippets when helpful
Overall assessment of architectural compliance

Focus on actionable feedback that helps maintain the codebase's architectural integrity and future maintainability.

Install review-staged and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

You are conducting a comprehensive code review of git staged files for this Electron (Forge + Vite) + React + TypeScript project. Analyze each staged file against the project's architectural and quality standards from `AI.md`. **Review Criteria:** ## Architecture & Boundaries - **Main / Preload / Renderer separation**: No Node/Electron APIs in renderer; keep preload as a narrow bridge. - **IPC discipline**: Prefer oRPC + Zod typed contracts (`src/ipc/**`, `src/actions/**`); avoid ad-hoc `ipcRenderer` usage. - **Routing**: Changes under `src/routes/` should respect TanStack Router conventions; don’t hand-edit `src/routeTree.gen.ts`. ## AI.md Rules Compliance - **File size & scope**: Keep files under ~300 lines; keep <=3 concerns per file; extract shared logic after 2+ uses. - **Imports**: Prefer `@/` absolute imports; avoid barrel files/re-export `index.ts` patterns. - **TypeScript**: Keep strict types; avoid `any` and unsafe assertions. - **Styling**: Prefer Tailwind + existing UI components (`src/components/ui/`) over ad-hoc CSS. - **Code quality**: Biome formatting/lint rules (2-space indent, single quotes, organized imports). ## Maintainability & Best Practices - **Security (Electron)**: - Avoid enabling `nodeIntegration` in renderer; keep `contextIsolation` enabled. - Never load/execute remote code in the renderer. - Preload should expose only minimal, explicit APIs (prefer `contextBridge`). - **Performance**: Avoid unnecessary IPC chatter; keep renderer work lightweight. - **Error Handling**: Clear error paths and user-facing feedback where appropriate. - **Naming**: Clear, descriptive variable and function names - **Dependencies**: Explicit dependency management, no hidden dependencies **Instructions:** 1. Get the list of staged files: `!git diff --staged --name-only` 2. For each staged file, read its content and analyze it thoroughly 3. Provide structured feedback with priority levels: - **P0 (Blockers)**: Critical issues that violate core principles and must be fixed - **P1 (Important)**: Significant improvements for maintainability and consistency - **P2 (Nits)**: Minor suggestions and optimizations **Output Format:** For each file, provide: - File path and brief summary - Priority-categorized issues with specific line references - Concrete recommendations with code snippets when helpful - Overall assessment of architectural compliance Focus on actionable feedback that helps maintain the codebase's architectural integrity and future maintainability.

{ "prompt": "You are conducting a comprehensive code review of git staged files for this Electron (Forge + Vite) + React + TypeScript project. Analyze each staged file against the project's architectural and quality standards from `AI.md`.\n\n**Review Criteria:**\n\n## Architecture & Boundaries\n- **Main / Preload / Renderer separation**: No Node/Electron APIs in renderer; keep preload as a narrow bridge.\n- **IPC discipline**: Prefer oRPC + Zod typed contracts (`src/ipc/**`, `src/actions/**`); avoid ad-hoc `ipcRenderer` usage.\n- **Routing**: Changes under `src/routes/` should respect TanStack Router conventions; don’t hand-edit `src/routeTree.gen.ts`.\n\n## AI.md Rules Compliance\n- **File size & scope**: Keep files under ~300 lines; keep <=3 concerns per file; extract shared logic after 2+ uses.\n- **Imports**: Prefer `@/` absolute imports; avoid barrel files/re-export `index.ts` patterns.\n- **TypeScript**: Keep strict types; avoid `any` and unsafe assertions.\n- **Styling**: Prefer Tailwind + existing UI components (`src/components/ui/`) over ad-hoc CSS.\n- **Code quality**: Biome formatting/lint rules (2-space indent, single quotes, organized imports).\n\n## Maintainability & Best Practices\n- **Security (Electron)**:\n - Avoid enabling `nodeIntegration` in renderer; keep `contextIsolation` enabled.\n - Never load/execute remote code in the renderer.\n - Preload should expose only minimal, explicit APIs (prefer `contextBridge`).\n- **Performance**: Avoid unnecessary IPC chatter; keep renderer work lightweight.\n- **Error Handling**: Clear error paths and user-facing feedback where appropriate.\n- **Naming**: Clear, descriptive variable and function names\n- **Dependencies**: Explicit dependency management, no hidden dependencies\n\n**Instructions:**\n1. Get the list of staged files: `!git diff --staged --name-only`\n2. For each staged file, read its content and analyze it thoroughly\n3. Provide structured feedback with priority levels:\n - **P0 (Blockers)**: Critical issues that violate core principles and must be fixed\n - **P1 (Important)**: Significant improvements for maintainability and consistency\n - **P2 (Nits)**: Minor suggestions and optimizations\n\n**Output Format:**\nFor each file, provide:\n- File path and brief summary\n- Priority-categorized issues with specific line references\n- Concrete recommendations with code snippets when helpful\n- Overall assessment of architectural compliance\n\nFocus on actionable feedback that helps maintain the codebase's architectural integrity and future maintainability.", "variables": [], "notes": "Review git staged files against AI.md rules and maintainability best practices", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/yuriyward/fix-grammar", "path": ".claude/commands/review-staged.md", "ref": "daed9b3b89131c27abb2dd2662fb44140d89e060", "url": "https://github.com/yuriyward/fix-grammar/blob/daed9b3b89131c27abb2dd2662fb44140d89e060/.claude/commands/review-staged.md", "key": "yuriyward/fix-grammar/.claude/commands/review-staged.md" } } }

review-staged

About

Architecture & Boundaries

AI.md Rules Compliance

Maintainability & Best Practices

Install review-staged and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews