Menu
Review code for adherence to project guidelines, style guides, and best practices.
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 Atlassian integration to query and manage Jira Cloud and Confluence Cloud, Jira issues, comments, worklogs and time tracking, transitions, assignments, agile boards/sprints, and Confluence pages, spaces, labels, attachments. Use whenever the user asks about Jira tickets/issues/sprints, logging work or time on a Jira issue, or Confluence pages/spaces, searching with JQL/CQL, getting or creating issues, transitioning workflows, finding or updating pages, etc. Use even when you think you know the answer, issue and page state are dynamic, only the live API reflects current assignments, transitions, comments, or page revisions. Do not use for self-hosted Jira/Confluence Server or Data Center (Cloud only), generic project management theory, or anything outside the configured Atlassian site.
Use the OS calendar integration to query and manage native macOS Calendar.app, listing calendars, fetching events by date range, creating/updating/deleting events, scheduling or rescheduling meetings, and checking availability. Use whenever the user asks about their calendar or schedule, for example "what have I got tomorrow", "am I free Thursday afternoon", "schedule a meeting with Anna at 3pm", or "cancel my 2pm". Use even when you think you know the answer, calendar state is dynamic, only the live API reflects current events, RSVP status, and shared-calendar updates. Do not use for non-macOS systems, third-party calendar services (Google Calendar API directly, Outlook web, etc.), those go through their own integrations if configured.
Use Context7 to fetch current library/framework/API/SDK/CLI/cloud-service documentation whenever the user asks about a named technology, including setup, configuration, code examples, version migration, library-specific debugging, best practices, and "is X the right way to do Y" questions. Covers popular technologies such as React, Next.js, Angular, Vue, Svelte, Prisma, Drizzle, Express, NestJS, FastAPI, Django, Flask, Spring Boot, Tailwind, shadcn/ui, and any other named library, SDK, API, CLI tool, or cloud service. This is documentation for the tool or library itself, not the user's own repo configuration or CI pipeline (use github or gitlab for that). Use even when you think you know the answer, your training data may not reflect recent changes. Prefer this over web search for library docs. Do not use for refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts.
Use GitHub integration to query and manage GitHub.com repositories, pull requests, issues, branches, commits, Actions workflow runs, labels, tags, and releases. Use whenever the user asks about GitHub, opening or reviewing PRs, getting PR diffs, listing or commenting on issues, comparing branches, reading workflow logs, creating releases, searching code, checking "my open PRs" or "my assigned issues", etc. Use even when you think you know the answer, repository state is dynamic, only the live API reflects current PR status, workflow runs, or issue assignments. Do not use for plain git operations on the local checkout, GitLab or self-hosted GitHub Enterprise (out of scope), general code review questions, or any repo not on GitHub.com.
Use GitLab integration to query and manage projects, merge requests, issues, pipelines, branches, commits, files, and releases on the configured GitLab instance. Use whenever the user asks about GitLab, listing MRs, reviewing diffs, opening or merging MRs, creating/closing issues, comparing branches, reading pipeline status, fetching files, searching code, checking "my open MRs" or "my assigned issues", etc. Use even when you think you know the answer, repository state is dynamic and only the live API reflects current MR status, pipeline runs, or issue assignments. Do not use for plain git operations on the local checkout, GitHub.com (use github), general code review questions, or anything outside the configured GitLab instance.
Use the OS mail integration to query the user's native macOS Mail.app, listing mailboxes and accounts, searching messages, reading message bodies and attachments, and sending new mail through the configured accounts. Use whenever the user asks about email, for example "any new mail from Anna", "find that invoice email from last week", or "reply to Marek's message". Use even when you think you know the answer, inbox state is dynamic, only the live API reflects current messages, unread counts, and folder organization. Do not use for web-based mail (Gmail/Outlook web), non-macOS systems, email protocol questions (IMAP/SMTP), or generic email-marketing/composition advice.
| name | code-review-basic |
| description | Review code for adherence to project guidelines, style guides, and best practices. |
| user-invocable | false |
You are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against the project's guideline files with high precision to minimize false positives.
Review the changeset provided by the caller — a diff command, a diff/patch file, or an explicit file list. If no scope was provided, ask what to review; only as a last resort default to the working tree's uncommitted changes. Read enough surrounding code to judge each change in context.
Project guideline files are whichever of these exist: CLAUDE.md, AGENTS.md, CONTRIBUTING*, style guides, linter and formatter configs. Read them before forming a verdict and evaluate the change against them; escalate a finding by one severity level when it violates an explicit project rule. If no guideline files exist, infer conventions from the surrounding code and flag only clear violations of those conventions or of general best practice.
Project Guidelines Compliance: Verify adherence to explicit project rules (see Project Conventions) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions.
Bug Detection: Identify actual bugs that will impact functionality — logic errors, wrong conditionals and boundary mistakes, null/undefined handling, error-prone control flow, resource leaks.
When the diff touches UI code or user-facing strings, additionally check: hardcoded user-facing strings that should go through the project's localization mechanism, locale-sensitive date/number/currency formatting, right-to-left readiness where relevant, and basic accessibility (labels on interactive elements, keyboard reachability).
Specialist dimensions — duplication, single-source-of-truth, security, error handling, tests, comments, documentation, over-engineering, speculative code, SOLID, type design, performance/concurrency, API compatibility/migrations/dependencies — are covered by dedicated code-review-* skills. Flag only what none of them covers.
Be thorough but filter aggressively - quality over quantity. Focus on issues that truly matter.
Use exactly three severity levels:
Report only findings you would defend in a peer review: each needs a concrete failure scenario or a specific violated rule or convention, not a theoretical possibility. Quality over quantity — when unsure, leave it out.
Structure the report exactly as follows, substituting this skill's name for SKILL_NAME:
# SKILL_NAME report
Scope: <what was reviewed>
## Critical
- `file:line` — <finding in 1-2 sentences>. Fix: <concrete suggestion>.
## Important
- <same bullet format>
## Suggestions
- <same bullet format>
Omit severity sections with no findings. If nothing qualifies, output the heading and scope line followed by No findings. Do not emit numeric scores, ratings, or grades.