requesting-code-review
Request and process code reviews with proper context. Use after completing significant implementation work.
Skills matching the name, description or GitHub author.
Request and process code reviews with proper context. Use after completing significant implementation work.
Comprehensive code review methodology. 4 layers (Correctness, Security, Performance, Style), severity classification, 80% confidence threshold.
Comprehensive Rust development expertise covering core principles, patterns, error handling, async programming, testing, and performance optimization. Use when working on Rust projects requiring guidance on: (1...
Best practices for conducting effective code reviews that improve code quality, share knowledge, and maintain team standards.
Interactive code review for agent iterations. Captures comments, tracks resolution status, and integrates with git diffs.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Performs systematic code review checking for correctness, maintainability, security, and best practices. Activates when user requests review, before creating PRs, or when significant code changes are ready. Ens...
This skill should be used when users want to search, discover, install, or manage Claude Code skills from the CCPM registry. Triggers include requests like "find skills for PDF", "search for code review skills"...
Comprehensive code review guidance for quality, performance, and architecture across all programming languages. Use when (1) User explicitly requests code review, (2) After writing significant code changes, (3)...
Deep, excruciating code review. Use anytime to analyze code for correctness, edge cases, security, performance, and design issues. Not tied to baseline—this is pure code analysis.
Code review specialist. Use when code needs review, before merging changes, or to assess code quality. Provides structured feedback with severity levels.
Automated code review workflow using OpenAI Codex CLI. This skill should be used when the user requests code to be reviewed using Codex CLI, or when implementing features that should be validated with automated...
Padrões e checklist para code review
Perform code review: detect risks, style issues, error handling gaps (report-only).
Building a positive code review culture that catches bugs, shares knowledge, maintains code quality, and builds team trust through effective review practices.
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Comprehensive Python development expertise covering modern best practices, type hints, FastAPI web development, async/await, testing, and performance optimization. Use when working on Python projects requiring...
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state...
Fluxo completo de Git: branches, commits, pull requests e code review
Test coverage check and creation workflow. Ensures tests exist for all features. Creates unit and E2E tests when missing following acceptance criteria. Use during validation before code review.
Use for code quality and engineering standards. Covers code style conventions, conventional commit messages, documentation standards (ADRs, API docs, changelogs), and security patterns (input validation, secret...
Use for code quality and engineering standards. Covers code style conventions, conventional commit messages, documentation standards (ADRs, API docs, changelogs), and security patterns (input validation, secret...
Use for code quality and engineering standards. Covers code style conventions, conventional commit messages, documentation standards (ADRs, API docs, changelogs), and security patterns (input validation, secret...
Use for code quality and engineering standards. Covers code style conventions, conventional commit messages, documentation standards (ADRs, API docs, changelogs), and security patterns (input validation, secret...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.