Skills matching the name, description or GitHub author.
Use when user mentions reviewing PRs, provides GitHub PR URLs/numbers, or discusses code review. Provides structured analysis of code quality, backward compatibility, security issues, test coverage, and unaddre...
Ensure features are developed according to specifications by validating implementation against API docs, database schemas, and acceptance criteria. Use before starting implementation, during code review, or whe...
Validates story implementations through testing, code review, and quality gate assessment. Uses testing skill for execution, checks standards compliance, and creates quality gate decisions (PASS/CONCERNS/FAIL/W...
Ensure code quality or perform code reviews through comprehensive checklists and standards enforcement.
Submit code review requests to multiple AI providers (GitHub Copilot, Anthropic Claude, OpenAI Codex, Google Gemini) and get patches back. Use when user says "code review", "review this code", "get a patch for"...
Perform thorough code reviews on pull requests, diffs, or code changes. Use when asked to review code, check a PR, or provide feedback on changes.
Analyze code quality, detect code smells, identify bugs, and provide improvement recommendations. Use when reviewing code, checking quality, analyzing complexity, or when user mentions code review, refactoring...
List PRs awaiting your review, checkout the branch, run linter, and generate a structured code review document.
Consult Oracle (GPT-5 Pro) for complex debugging, architecture questions, or code review. Use when stuck on a problem, need a second opinion, or want deep analysis of code. Invoked when user says "ask the oracl...
Use this skill when discussing production readiness, severity levels (P0-P4), code review standards, or FAANG-level engineering practices. Triggers: "production ready", "P0", "P1", "severity levels", "code rev...
Inline orchestration workflow for code review with Beads integration. Provides comprehensive analysis of issues (bugs) AND improvements (recommendations), issue creation, priority-based fixing, and verification...
Use when reviewing code or PRs in the llama-stack repository (llamastack/llama-stack on GitHub). Provides specialized knowledge about Llama Stack's architecture, testing patterns (recordings folders), backward...
Use when reviewing OpenAI API usage, answering questions about OpenAI endpoints, or validating implementations against the official API specification. Provides expert knowledge on chat completions, embeddings,...
Interactive code review for agent iterations. Captures comments, tracks resolution status, and integrates with git diffs.
Code review using multiple AI models concurrently
Use Codex CLI (OpenAI) for code consultation and review. Triggers: "codex", "ask codex", "code review", "review this" Use cases: (1) Message/copy review, (2) Code review, (3) Design consultation, (4) Bug invest...
Full validation workflow for QA agent. Runs automated checks (type-check, lint, test, build) and browser testing with E2E tests. Use when validating implementation after code review.
Collects and organizes code review feedback into actionable tasks.
Review implementation quality and regression risks via claude-delegator (Code Reviewer expert). Use after implementation for complex tasks, refactors, or API changes.
Validate integration impact and regression risks via claude-delegator (Code Reviewer expert). Use for complex tasks or API integration.
manage pull request code reviews, approvals, comments, and feedback cycles
OMCC (Coder-Reviewer-Advisor) collaboration for code and document tasks. Use when: writing/modifying code, editing documents, implementing features, fixing bugs, refactoring, or code review. 协调 Coder 执行代码...
Use when reviewing code, verifying implementations, checking security, validating acceptance criteria, or conducting code reviews for a completed implementation.
Best practices for conducting effective code reviews that improve code quality, share knowledge, and maintain team standards.
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.