← All skills

code-reviewer

CommunityMIT

You MUST use this when asked to review code: a pull request, a branch, a commit, staged or uncommitted changes, or \"check this before I merge\". Scopes the review to the diff, reads the surrounding code, hunts for real bugs (correctness, security, data loss, concurrency, broken callers, missing tests), verifies every finding against the code before reporting it, and returns a short severity-ranked list with a concrete failure scenario for each. Use it for any language; not for writing new code or for style-only cleanups.

The ZIP contains only this skill. It lives on GitHub Releases of the public orlandoneto/agent-skills repo — Ontoom is the showcase. A daily crawler refreshes the catalog.

How to install

  1. Download the ZIP and extract the skill folder.
  2. Cursor: .agents/skills/aitmpl-code-reviewer/ or .cursor/skills/aitmpl-code-reviewer/
  3. Claude Code: .claude/skills/aitmpl-code-reviewer/
  4. Other AIs: .agents/skills/aitmpl-code-reviewer/
cursorclaude-codecodexgeminiany

Source / credits: davila7/claude-code-templates

Other skills in this collection

Claude Code Templates

  • codex

    Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering.

  • codex-review

    Professional code review with auto CHANGELOG generation, integrated with Codex AI

  • Command Development

    This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

  • command-creator

    This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.

  • competitive-ads-extractor

    Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

  • competitor-alternatives

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.