Menu
Use when reviewing a diff or pull request — find correctness bugs first, then reuse/simplification cleanups, and report each finding with a concrete failure scenario ranked by severity.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when writing or reviewing OpenAidy addon UI code (app/index.html, app/index.js) that calls sdk.ui.* — covers component mounting semantics and composed usage patterns beyond the one-line reference in addon_create's tool description.
Use when calling external REST APIs or querying databases on the user's behalf through available tools or MCP servers — read-only by default, parametrized queries, and confirmation before any write.
Use when reading, extracting from, or generating real-world document files — PDFs, spreadsheets (CSV/Excel/Sheets), and slide decks — with available tools; preserve the source and verify the output.
Use when working with calendars — checking availability, finding meeting times, and creating or updating events through an available calendar integration — with careful timezone handling and confirmation before inviting others.
Use when posting to chat or email on the user's behalf — Slack, Discord, Telegram, or mail — through an available integration. Get the recipient and content right, and confirm before anything goes out.
Use when a task needs a real browser — navigating sites, filling and submitting forms, clicking through flows, extracting page data, or taking screenshots — driving whatever browser tool or MCP server is available.
| name | Code Review |
| description | Use when reviewing a diff or pull request — find correctness bugs first, then reuse/simplification cleanups, and report each finding with a concrete failure scenario ranked by severity. |
| version | 1.0.0 |
A review's job is to catch what tests and the type checker won't. Read the diff for correctness first; treat style and cleanup as secondary.
await, unhandled promise rejection.if (!count) when 0 is valid).catch that should propagate.Every finding needs a concrete failure scenario, not a vibe:
src/foo.ts:42—parseIdreturnsundefinedfor empty input, but the caller indexes into it →TypeErrorwhen the list is empty.
Don't flag style the linter already enforces, don't rewrite to personal
taste, and don't invent requirements. A short list of real bugs beats a
long list of nitpicks. See references/review-checklist.md.