Portail QC Automatisé

VérifiéSûr

Système de contrôle qualité parallèle avec 5 agents spécialisés (révision, simplification, cohérence, robustesse, périmètre) validant tous les changements avant commit.

Spar Skills Guide Bot
DeveloppementIntermédiaire
2002/06/2026
Claude Code
#quality-gate#code-review#parallel-agents#git-diff

Recommandé pour

Notre avis

Un portail qualité qui lance cinq agents d'IA en parallèle pour examiner les changements de code et exiger que tous passent avant de fusionner.

Points forts

  • Revue simultanée sous plusieurs angles (côté code, simplification, cohérence, robustesse, périmètre).
  • Retour structuré en JSON avec verdict clair (pass/échec) et liste d'issues.
  • Gère les gros diffs en découpant la simplification fichier par fichier.
  • Réduction des faux négatifs grâce à une retry en cas de JSON invalide.

Limites

  • Dépend fortement de la qualité des modèles d'IA (sonnet et haiku).
  • Peut manquer le contexte global si le diff est complexe ou mal décrit.
  • Nécessite une configuration initiale (branche de référence, récupération du diff).
Quand l'utiliser

Avant chaque commit ou merge pour garantir que les changements respectent les standards de qualité du projet.

Quand l'éviter

Pour des modifications triviales ou en phase de prototypage rapide où la rigueur serait contre-productive.

Analyse de sécurité

Sûr
Score qualité90/100

The skill only uses Bash to run 'git diff' and file listing, which are non-destructive. It spawns review agents that analyze code but perform no harmful actions. No external network access, destructive commands, or exfiltration is instructed.

Aucun point d'attention détecté

Exemples

Run QC gate on current branch
Run the QC gate on the current branch changes against main.
Run QC with custom task description
Run QC gate on my changes. The task was: 'Add input validation for email field'.

name: qc description: Quality gate. 5 parallel agents review changes. All must pass. allowed-tools: Task, Bash, Read, Grep, Glob

QC Gate

Setup

DIFF=$(git diff main)
FILES=$(git diff main --name-only)
TASK="{task description or 'general changes'}"

Read 1-2 unmodified files from same directories for pattern context.

Agents

Spawn all 5 in parallel. All output raw JSON only, no markdown.

1: Code Review (sonnet)

DIFF: ${DIFF}

- Descriptive naming?
- Errors caught with useful messages?
- No hardcoded values, commented code, debug statements?
- No TODO without ticket ref?
- No obvious bugs?
- No useless comments?

{"pass": bool, "issues": [...]}

2: Simplification (sonnet)

DIFF: ${DIFF}

- Is this overcomplicated? Can I solve the same problem in a simpler manner?
- Can I reduce indirection?
- Can I reduce surface area?
- Premature abstraction? Premature Optimization? YAGNI violations?
- Dead code?
- Three similar lines > one abstraction

{"pass": bool, "issues": [...]}

3: Consistency (sonnet)

DIFF: ${DIFF}
PATTERNS: ${PATTERN_FILES}

- Matches existing codebase patterns?
- Proper types, no any, no unsafe casts?
- Idiomatic error handling?
- Changes internally consistent?
- Is logic isolated and composable?
- Are there existing tests if neccesary?

{"pass": bool, "issues": [...]}

4: Robustness (sonnet)

TASK: ${TASK}
DIFF: ${DIFF}

- Actually solves the problem?
- Edge cases: empty, null, zero, negative, boundaries, concurrency?
- Regression risk: changed signatures, shared state, removed exports?
- Maintains API contracts?

{"pass": bool, "issues": [...]}

5: Scope (haiku)

TASK: ${TASK}
FILES: ${FILES}
DIFF: ${DIFF}

- Solved the problem or just the symptom?
- Changes unrelated to task?
- Unnecessary refactoring?

{"pass": bool, "issues": [...]}

Results

| Check | Verdict | Issues | |-------|---------|--------| | Code Review | ✓/✗ | ... | | Simplification | ✓/✗ | ... | | Consistency | ✓/✗ | ... | | Robustness | ✓/✗ | ... | | Scope | ✓/✗ | ... |

ALL PASS: Ready to commit.

ANY FAIL: List issues, fix them, run /qc again.

Same issue 3x: Escalate to user.

Notes

  • Invalid JSON? Retry once. Still broken? Mark fail.
  • Large diffs (>500 lines): run simplification file-by-file.
Skills similaires