code-review-checklist
Comprehensive code review checklists for backend and frontend code.
Skills correspondant au nom, à la description ou à l’auteur GitHub.
Comprehensive code review checklists for backend and frontend code.
Perform thorough, constructive pull request reviews using parallel specialized agents. Use when user wants to review a PR, provide code review feedback, or assess code changes. Features confidence-scored issues...
Quick code review for files or recent changes, checking for bugs, best practices, and potential improvements
Comprehensive code review for Golang CLI applications. Produces an actionable checklist covering error handling, CLI framework patterns (Cobra/urfave), testing, performance, security, and Go idioms. TRIGGERS:...
Interactive code review using Google Gemini 3.0 Flash with Conventional Comments methodology. MANDATORY - runs automatically after every code implementation (Edit, Write tools). Provides numbered issues for sel...
Code review workflows with Codex CLI including automated reviews, diff analysis, and PR improvements. Use for code review, quality checks, or automated improvement suggestions.
Multi-perspective code review using Claude, Gemini, and Codex as specialized agents. 5-dimensional analysis (security, performance, maintainability, correctness, style) with LLM-as-judge consensus, quality scor...
GitHub PR utilities for code review workflows
Automated PR code review with multi-agent analysis
Capable of performing comprehensive code reviews on git commits. Analyzes commit changes, investigates side effects in the codebase, and categorizes findings by severity levels (critical, major, minor, nit).
Creates GitHub Pull Requests with existing PR detection, branch pushing, and intelligent title/body generation. Use when user requests to create pull request, open PR, update PR, push for review, ready for revi...
Comprehensive parallel code review using 5 specialized subagents: general, architectural, TypeScript, product/vision, and TDD/beads compliance
Reviews pull requests and code changes for quality, security, and best practices. Use when user asks for code review, PR review, or mentions reviewing changes.
Run before marking coding tasks complete - validates code quality via IDE diagnostics, code review rules, and tests with fast-feedback short-circuiting
Pre-PR code review for branch changes. Use when user wants to review changes before opening a PR, asks to check their branch for issues, or mentions code review. Analyzes diff against base branch for code quali...
Use when auditing code for AI authorship, reviewing acquisitions/contractors, verifying academic integrity, or during code review - provides systematic tiered framework for detecting fully AI-generated AND AI-a...
Code review agent based on Sandi Metz's object-oriented design principles from "Practical Object-Oriented Design in Ruby" and "99 Bottles of OOP". Use when users request code reviews, ask about OO design princi...
Comprehensive Ruby and Rails code review using Sandi Metz rules and SOLID principles. Automatically runs rubycritic and simplecov, analyzes changed files in current branch vs base branch, identifies OOP violati...
Elite code review agent for comprehensive analysis of code quality, security, performance, and architecture. Use when reviewing PRs, analyzing code changes, checking for bugs, security vulnerabilities, or perfo...
Use when the user needs technical research, architecture validation, documentation generation, or code review. Default is read-only mode, but can enable auto-approve (-y) for code changes.
Automatically triggered for code reviews, PR analysis, and quality checks. Use when reviewing changes, checking code quality, or preparing commits.
Code quality - patterns, testing, maintainability. Use for code review.
Perform systematic code reviews following best practices and team standards
Best practices for performing thorough, constructive code reviews. Use when reviewing PRs to ensure quality feedback that improves code and helps developers grow.
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é.