Notre avis
Analyse critique des retours d'une revue de code par un pair, en vérifiant leur validité et en priorisant les corrections.
Points forts
- Encourage une évaluation objective et contextuelle des commentaires
- Permet de distinguer les vrais bugs des malentendus architecturaux
- Facilite la création d'un plan d'action priorisé
Limites
- Nécessite une bonne connaissance du projet pour évaluer correctement
- Peut être biaisé si l'utilisateur manque d'objectivité
- Ne remplace pas une discussion humaine approfondie
Lorsque vous recevez des retours d'une revue de code d'un autre lead et que vous devez les évaluer avant d'agir.
Si les retours sont déjà validés et ne nécessitent pas d'analyse critique, ou si vous n'avez pas accès au code concerné.
Analyse de sécurité
SûrThe skill is a meta-instruction for evaluating peer review feedback. It contains no executable commands, no instructions to manipulate files or network, and no obfuscated payloads. It purely describes a cognitive process.
Aucun point d'attention détecté
Exemples
A different team lead within the company has reviewed the current code/implementation and provided findings below. Important context:
- **They have less context than you** on this project's history and decisions
- **You are the team lead** - don't accept findings at face value
- Your job is to critically evaluate each finding
Findings from peer review:
1. The error handling in the payment module is insufficient. It doesn't catch network timeouts properly.
2. The caching layer is not thread-safe and may cause race conditions.
3. The database query in UserRepository is missing an index on the email column.
---
For EACH finding above:
1. **Verify it exists** - Actually check the code. Does this issue/bug really exist?
2. **If it doesn't exist** - Explain clearly why (maybe it's already handled, or they misunderstood the architecture)
3. **If it does exist** - Assess severity and add to your fix plan
After analysis, provide:
- Summary of valid findings (confirmed issues)
- Summary of invalid findings (with explanations)
- Prioritized action plan for confirmed issuesA different team lead within the company has reviewed the current code/implementation and provided findings below. Important context:
- They have less context than you on this project's history and decisions
- You are the team lead - don't accept findings at face value
- Your job is to critically evaluate each finding
Findings from peer review:
[PASTE FEEDBACK FROM OTHER MODEL]
For EACH finding above:
- Verify it exists - Actually check the code. Does this issue/bug really exist?
- If it doesn't exist - Explain clearly why (maybe it's already handled, or they misunderstood the architecture)
- If it does exist - Assess severity and add to your fix plan
After analysis, provide:
- Summary of valid findings (confirmed issues)
- Summary of invalid findings (with explanations)
- Prioritized action plan for confirmed issues
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.