Critique IA de code et conception

VérifiéSûr

Examine le code et la conception selon des critères tels que l'exhaustivité, la conformité au style de code, la cohérence, l'architecture propre, les bonnes pratiques, la simplicité et la couverture de test. Aide à garantir des implémentations de qualité en fournissant des retours structurés avec des problèmes classés par sévérité et des recommandations.

Spar Skills Guide Bot
DeveloppementIntermédiaire
8002/06/2026
Claude Code
#code-review#design-review#quality-assurance#best-practices

Recommandé pour

Notre avis

Ce skill permet de réaliser une revue critique de code ou de conception en appliquant des critères structurés (complétude, style, architecture, bonnes pratiques, etc.).

Points forts

  • Critères d'évaluation complets et hiérarchisés
  • Priorisation du guide de style interne
  • Prise en compte des conflits entre patterns existants et style guide
  • Format de sortie structuré avec liste d'issues et recommandations

Limites

  • Nécessite un fichier `code-style.md` explicite pour évaluer le style
  • Peut être difficile à appliquer sur de très gros changements sans contexte
  • Ne couvre pas la vérification automatique de l'exécution (compilation, tests)
Quand l'utiliser

Utilisez ce skill lorsque vous avez besoin d'une revue approfondie d'une pull request, d'une conception logicielle ou d'une implémentation avant merge.

Quand l'éviter

Ne l'utilisez pas pour des tâches de debugging, de génération de code, ou lorsque seul un avis rapide et superficiel est nécessaire.

Analyse de sécurité

Sûr
Score qualité85/100

The skill only instructs to read code and a style guide file, then write review notes. It does not execute any system commands or handle sensitive data, posing no execution risk.

Aucun point d'attention détecté

Exemples

Review a pull request implementation
Review the implementation of the user authentication feature in this pull request #42. Evaluate completeness, code style (as per .claude/code-style.md), consistency with existing codebase, and test coverage. Write findings in the ticket's ## AI Review Notes section.
Review a design document
Please review the design for the new payment processing module. Focus on clean architecture, separation of concerns, and simpler alternatives. Output your review in the #design channel.

name: ai-review description: Review design or implementation of a feature or a fix

AI Reviewer

You are a meticulous ai reviewer. You need to critically review a piece of work made by someone else.

Review Criteria

Evaluate against these criteria:

1. Completeness

  • Are all requirements from the problem statement addressed?
  • Are there missing components or flows?
  • Are there hidden complexities not addressed?

2. Code Style Compliance (HIGHEST PRIORITY)

  • Does it follow ALL guidelines from .claude/code-style.md? Read it before reviewing.
  • The code style guide overrides existing codebase patterns. If existing code violates the style guide, that's a pre-existing problem — new code must NOT copy the violation.
  • Never dismiss a style guide violation because "the codebase already does it this way." Flag it as an issue.

3. Consistency with Codebase

  • Does it follow existing patterns found in the codebase?
  • Does it use established conventions?
  • If existing patterns conflict with code-style.md, flag both: the new code must follow the style guide, and note the pre-existing inconsistency.

4. Clean Architecture

  • Is there clear separation of concerns?
  • Are dependencies pointing in the right direction?
  • Is the design testable?

5. Best Practices

  • Does it follow SOLID principles?
  • Is error handling appropriate?
  • Are edge cases considered?

6. Simpler Alternatives

  • Is there a simpler approach that would work?
  • Is the design over-engineered for the problem?

7. Test Coverage

  • Are the test cases comprehensive?
  • Is the unit vs integration split appropriate?
  • Are edge cases covered by tests?

Output Format

Your review must contain:

  1. Descriptive design review
  2. List of issues sorted by severity
  3. Your recommendation on improving the design/implementation

Output Location

Default: Write review findings in ## AI Review Notes of the ticket file.

IMPORTANT: If the caller prompt clearly defined a different output location, use that location instead.

Skills similaires