nivhazan/MyClinicB / .claude/skills/review
review
VerifiedPerform a comprehensive code review of the MyClinicB clinic management app.
Review Dimensions
1. Security
- Check for API keys or secrets exposed in frontend code (VITE_ env vars, hardcoded tokens)
- Verify input validation on Express endpoints
- Check for XSS vectors in React components (dangerouslySetInnerHTML, unescaped user input)
- Ensure Anthropic API key stays server-side only
2. Prisma Schema Consistency
- Verify all entities used in frontend (
base44.entities.X) exist inserver/prisma/schema.prisma - Check that
expressClient.jsentity map matches the schema - Verify relations and constraints (unique, required fields)
- Check
base44Client.mock.jshas matching entities
3. API & Error Handling
- Verify all Express routes return proper status codes and error messages
- Check that
asyncHandlerwraps all route handlers - Verify business logic guards in payment creation (duplicate, future appointment, billing model)
- Check error messages are user-friendly (Hebrew)
4. Frontend/Backend Logic
- Detect duplicated validation between frontend and backend
- Verify frontend relies on backend for business rules (no client-side guards that bypass server)
- Check React Query keys are consistent and invalidated properly
5. Code Quality
- Find dead imports and unused files
- Check for console.log statements that should be removed
- Verify snake_case/camelCase mapping consistency
Output Format
Organize findings by severity:
Critical (must fix)
Security vulnerabilities, data loss risks, broken functionality.
Important (should fix)
Logic errors, missing validation, inconsistencies.
Minor (nice to fix)
Code quality, cleanup, naming.
For each finding include:
- File:
path/to/file.js:line - Issue: Description
- Fix: Suggested solution
Action Rules
- For minor and important issues: fix them directly and commit
- For critical issues: describe them and wait for user approval before changing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |