review
Automates a multi-dimensional security and code quality review for the MyClinicB app.
Install
mkdir -p .claude/skills/review-nivhazan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13255" && unzip -o skill.zip -d .claude/skills/review-nivhazan && rm skill.zipInstalls to .claude/skills/review-nivhazan
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Perform a comprehensive code review of the MyClinicB clinic management app.Key capabilities
- →Check for exposed API keys or secrets
- →Verify input validation on Express endpoints
- →Ensure Prisma schema consistency with frontend entities
- →Verify API error handling and status codes
- →Detect duplicated validation between frontend and backend
- →Identify dead imports and unused files
How it works
The skill performs a complete code review across security, Prisma schema consistency, API error handling, frontend/backend logic, and code quality dimensions, organizing findings by severity.
Inputs & outputs
When to use review
- →Reviewing security vulnerabilities
- →Checking Prisma schema
- →Refactoring API routes
About this skill
Perform 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
When not to use it
- →When reviewing a project other than MyClinicB
- →When the review is not focused on security, Prisma, API, or code quality dimensions
- →When the user wants to fix critical issues without prior approval
Limitations
- →Limited to the MyClinicB clinic management app
- →Critical issues require user approval before changes are made
- →Review dimensions are fixed to Security, Prisma, API, Frontend/Backend Logic, and Code Quality
How it compares
This review is tailored specifically to the MyClinicB application, focusing on its particular tech stack and common issues, unlike a generic code quality check.
Compared to similar skills
review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| review (this skill) | 0 | 5mo | No flags | Intermediate |
| lint-and-validate | 6 | 6mo | Review | Beginner |
| fullstack-guardian | 1 | 3mo | No flags | Advanced |
| vercel-known-pitfalls | 1 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
lint-and-validate
davila7
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
fullstack-guardian
Jeffallan
Use when implementing features across frontend and backend, building APIs with UI, or creating end-to-end data flows. Invoke for feature implementation, API development, UI building, cross-stack work.
vercel-known-pitfalls
jeremylongshore
Execute identify and avoid Vercel anti-patterns and common integration mistakes. Use when reviewing Vercel code for issues, onboarding new developers, or auditing existing Vercel integrations for best practices violations. Trigger with phrases like "vercel mistakes", "vercel anti-patterns", "vercel pitfalls", "vercel what not to do", "vercel code review".
dependency-updater
davila7
Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues.
dependency-upgrade
pinkpixel-dev
Master major dependency version upgrades, compatibility analysis, staged upgrade strategies, and comprehensive testing approaches.
fix-dependabot-alerts
microsoft
Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.