agentleFS
ultimatethemedev-bitultimatethemedev-bit/claude-vitrine-kit/.claude/skills/code-review/SKILL.md

code-review

Skill0 starsChanged 57 days agoMITView on GitHub

Étape 3 (contrôle) de la méthode "reproduire un site vitrine depuis des images IA" : une fois le style validé par l'utilisateur, passe le code en revue — correct, DRY (aucune répétition inutile), sans erreurs, cohérent. Liste les problèmes et les corrige, sans toucher au rendu visuel validé. DÉCLENCHE quand le style d'un site est validé et avant de passer aux effets/à la mise en ligne : "vérifie le code", "code review", "est-ce que le code est propre", "on passe à la revue de code".

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • PydanticSkill

    add-new-model

    Add support for a newly-released language or image generation model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5, openai:gpt-image-2). Use when a provider ships a new model id and you need to wire literals, profile flags, adapters, and tests to recognize it. Handles SDK-lag, gateway list conventions, capability probing, and direct image-model geometry.

    Also in 9 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 5 projects that use this

  • Microsoft AzureSkill

    azsdk-common-apiview-feedback-resolution

    Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    azsdk-common-generate-sdk-locally

    Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.

    Also in 6 projects that use this

  • +4 more from dzhng
  • +2 more from Azure

The file

Files
SKILL.md

code-review — vérifier le code (étape 3)

Le style est validé par l'utilisateur : on fige le rendu et on nettoie le code sans changer l'apparence. But : un code correct, propre et maintenable avant d'ajouter les effets.

Ce qu'on vérifie

  • Correct : le code fait ce qu'il doit, pas de bug, pas d'erreur console au build/run.
  • DRY : les styles/patterns répétés à l'identique dans plusieurs sections sont factorisés (mis en commun) plutôt que copiés-collés. On repère les blocs dupliqués.
  • Cohérent : mêmes conventions partout (nommage, structure des composants, tokens réutilisés au lieu de valeurs en dur), breakpoint unique respecté.
  • Propre : pas de code mort, pas de styles inutilisés, pas de valeurs magiques non expliquées.

Déroulé

  1. Parcourir le code section par section + les fichiers communs.
  2. Lister les problèmes trouvés (répétitions, incohérences, erreurs, code mort), classés par importance.
  3. Corriger — en vérifiant après chaque correction que le rendu n'a pas bougé (screenshot avant/après si besoin) : on ne casse pas le visuel validé.
  4. Rendre un état clair : ce qui a été corrigé, ce qui reste éventuellement à décider avec l'utilisateur.

Garde-fou

La revue ne change pas le design validé. Si une amélioration de code impliquait un changement visuel, on le signale à l'utilisateur au lieu de l'appliquer d'office.

→ Une fois le code propre : on passe aux effets (faire vivre le site).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.