GitHub
git-workflow
Git workflow and pull request specialist. Use when creating PRs, managing branches, establishing git conventions, or improving code review processes.
☆ 122View skill
Search results for “code review”
Skills matching the name, description or GitHub author.
Categories: Documentation
Browse skills
GitHub
comprehensive-code-review
This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREME...
☆ 122View skill
GitHub
code-review
Expert code review specialist for quality, security, and maintainability. Use when reviewing code changes, ensuring high development standards, or conducting security audits. Provides actionable feedback organi...
☆ 122View skill
GitHub
code-review
Performs thorough code reviews with focus on best practices, security, performance, and maintainability. Use this skill when reviewing pull requests, auditing code quality, or getting feedback on implementation...
☆ 118View skill
GitHub
codex-code-reviewer
Systematic code review workflow using zen mcp's codex tool. Use this skill when the user explicitly requests "use codex to check the code", "check if the recently generated code has any issues", or "check the c...
☆ 115View skill
GitHub
code-review
Comprehensive code review methodology with severity classification and confidence thresholds
☆ 108View skill
GitHub
code-review-assistant
Perform structured, actionable code reviews for Python code with clear findings and suggestions.
☆ 108View skill
GitHub
code-review-reception
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
☆ 106View skill
GitHub
team-collaboration
Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
☆ 106View skill
GitHub
requesting-code-review
Structured code review workflow for SRTD development. Use after implementing features, fixing bugs, or before merging to main. Ensures production-readiness through systematic review.
☆ 103View skill
GitHub
code-review-playbook
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Use when reviewing PRs or st...
☆ 98View skill
GitHub
evidence-verification
Use when completing tasks, code reviews, or deployments to verify work with evidence. Collects test results, build outputs, coverage metrics, and exit codes to prove work is complete.
☆ 98View skill
GitHub
code-review-reception
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
☆ 96View skill
GitHub
standards-enforcement
Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring lint...
☆ 95View skill
GitHub
critical-code-reviewer
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this...
☆ 94View skill
GitHub
python-backend-reviewer
Expert Python backend code reviewer that identifies over-complexity, duplicates, bad optimizations, and violations of best practices. Use when asked to review Python code quality, check for duplicate code, anal...
☆ 91View skill
GitHub
wp-performance-review
WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strateg...
☆ 91View skill
GitHub
matrix-code-review
This skill should be used when the user asks to "review this code", "review PR", "code review", "review staged changes", "blast radius analysis", "check impact of changes", or needs comprehensive context-aware...
☆ 87View skill
GitHub
code-review
Comprehensive code review combining PR review, self-review, and quality checks. Supports reviewing PRs by number or comparing branches.
☆ 87View skill
GitHub
ringrequesting-code-review
Gate 4 of development cycle - dispatches 5 specialized reviewers (code, business-logic, security, test, nil-safety) in parallel for comprehensive code review feedback.
☆ 86View skill
GitHub
ringsubagent-driven-development
Autonomous plan execution - fresh subagent per task with automated code review between tasks. No human-in-loop, high throughput with quality gates.
☆ 86View skill
GitHub
static-code-analysis
Implement static code analysis with linters, formatters, and security scanners to catch bugs early. Use when enforcing code standards, detecting security vulnerabilities, or automating code review.
☆ 84View skill
GitHub
code-review-analysis
Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing...
☆ 84View skill
GitHub
agent-architect
Create and refine OpenCode agents via guided Q&A. Use proactively for agent creation, performance improvement, or configuration design. Examples: - user: "Create an agent for code reviews" → ask about scope, p...
☆ 81View skill
Popular categories
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.