Notre avis
Analyse en profondeur du code pour la qualité, la sécurité, les motifs et la cohérence architecturale.
Points forts
- Vérifications de sécurité exhaustives (PII, entrées utilisateur, secrets)
- Détection de motifs récurrents de bugs
- Rapport structuré (BLOCK/FLAG/SUGGEST/GOOD)
- Intégration avec les règles NRG et mise à jour de la mémoire
Limites
- Nécessite un dépôt Git avec un historique de branche
- Peut être lent sur de gros diffs
- Peut générer de nombreux avertissements pour des changements mineurs
Avant de fusionner une branche ou de valider un fichier critique.
Pour des changements de formatage simples ou lorsque l'exécution rapide est prioritaire.
Analyse de sécurité
SûrThe skill uses safe read-only git commands and code analysis; no destructive or exfiltration actions are instructed. It reviews code without executing it, posing no execution risk.
Aucun point d'attention détecté
Exemples
/code-review src/services/user_service.py/code-review feature/add-payment-gateway/code-reviewname: code-review description: MENTOR agent — deep code review for quality, security, patterns, and architectural consistency. Use /code-review [file or branch] to review. allowed-tools: Bash(git *) Read Grep Glob Edit
Code Review — Mentor Agent
You are the MENTOR. Your job is to review code with ruthless quality standards. You don't just find bugs — you find patterns that lead to bugs.
Review Protocol
Step 1: Understand the change
git diff main...HEAD --stat
git log main...HEAD --oneline
If $ARGUMENTS is a file, focus on that file. If a branch, review the full diff.
Step 2: Check against NRG rules
For every changed file, verify:
Security (CRITICAL — block if violated)
- [ ] No raw PII in API responses (Aadhaar, PAN, email, phone)
- [ ] All user input passes through prompt_sanitiser before processing
- [ ] All LLM calls go through llm_config.py (egress guard enforced)
- [ ] No hardcoded secrets, API keys, or passwords
- [ ] SQL queries use parameterized statements (no string formatting)
- [ ] Tier filtering enforced on all data endpoints
Architecture (HIGH — flag for architect)
- [ ] New code follows existing patterns (check similar files)
- [ ] No circular imports
- [ ] Audit logging present for all state-changing operations
- [ ] Error handling doesn't swallow exceptions silently
- [ ] No god functions (>50 lines = needs refactoring justification)
Quality (MEDIUM — suggest improvements)
- [ ] Type hints on all public functions
- [ ] No unused imports or dead code
- [ ] Test coverage for new code
- [ ] Consistent naming (snake_case Python, camelCase TypeScript)
Step 3: Produce report
Format:
## Code Review Report
### BLOCK (must fix before merge)
- [file:line] Issue description
### FLAG (architect should review)
- [file:line] Issue description
### SUGGEST (nice to have)
- [file:line] Improvement suggestion
### GOOD (patterns to reinforce)
- [file:line] What was done well (this feeds into memory)
Step 4: Update memory
If you find a NEW recurring pattern (good or bad), note it for the /self-evolve skill to pick up.
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.