code-review
Use when requesting code review, receiving code review feedback, before merging, or when handling reviewer suggestions - covers both giving and receiving review
Skills correspondant au nom, à la description ou à l’auteur GitHub.
Use when requesting code review, receiving code review feedback, before merging, or when handling reviewer suggestions - covers both giving and receiving review
Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement
Follow project-wide development conventions including consistent project structure, clear documentation, version control best practices, environment configuration, dependency management, code review processes,...
Reviews p5.js tower defense game code for architecture patterns, manager responsibilities, performance issues, and code quality. Use when reviewing enemies, towers, managers, renderers, or asking for code revie...
Help address GitHub PR review comments. Use when the user mentions PR reviews, code review feedback, reviewer comments, or needs to resolve review threads.
Simplify code for clarity, consistency, and maintainability while preserving all functionality. Use after completing a coding task or after passing code review to polish the implementation.
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
Performs strict code review with comprehensive validation
Code review and audit agent for pull requests and code quality
Execute codex CLI as sub-agent for thorough code reviews (codex's specialty), alternative approaches when stuck, or complex problems requiring extended investigation. Note that inference takes significant time.
Reviews code for quality, security, and maintainability. Use after writing/modifying code, before commits, or when asked to review changes. Triggers on "review code", "check my changes", "code review".
This skill should be used when the user asks to "review code with codex", "run codex review", "check code quality", "codex レビュー", mentions "レビューゲート", or before git commit/PR/merge/release. Performs i...
Technical evaluation of code review feedback. Use when receiving review feedback - requires verification before implementing, no performative agreement, push back when technically wrong.
Multi-agent spec review with parallel Claude/OpenCode reviewers. Use after spec-create or standalone via /spec.review.
Code review methodology. Use when reviewing code locally or preparing for a PR review.
Orchestrate multi-agent development workflows. Use when starting a new feature to coordinate architecture design, implementation, code review, and release through specialized sub-agents.
Follow project-wide development conventions for file structure, documentation, version control, environment configuration, and code review processes. Use this skill when organizing project files and directories...
Generates a code review checklist for the Code Reviewer agent
Use for security, quality, and PM compliance review before merging strategy code. Supports Ralph Loop iterative mode for backtest optimization. Runs PM audit, security audit, code review, backtest validation, a...
Systematic code review for TapScore focusing on code smells, duplication, architecture violations, and security issues. Use when reviewing code changes before commit or merge. Provides constructive feedback wit...
Automated TFVC code review for Azure DevOps changesets with Snyk security scanning and Notion integration
Phased Implementation Supervisor to coordinate coding and code review subagents. Use this skill when the user has an implentation plan file and wants to execute it phase by phase with build verification, testin...
Critical code review methodology. Use when reviewing code, PRs, or changes to enforce rigorous review standards.
Python code review specialist. Use when reviewing Python code, checking for bugs, security issues, or ensuring code quality standards.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.