octocode-pull-request-reviewer_skill

Overview

This skill performs expert pull request reviews using Octocode MCP tools to deliver evidence-backed findings on defects, security, performance, and architectural impact. It enforces a strict pre-flight dependency check, follows a multi-phase inspection flow, and produces actionable comments with precise code citations. Reviews can operate in Quick or Full mode based on file count and risk.

How this skill works

The reviewer first verifies Octocode MCP tool availability and fetches the PR metadata and diffs via githubSearchPullRequests. It discovers project review guidelines, asks the user for any additional context, then runs a structured analysis pipeline: search → locate → trace → read. All code reads and traces use Octocode MCP (github* or local* + LSP when applicable), producing domain-specific findings with linked file references and confidence levels.

When to use it

• When you ask “review a PR”, “review pull request”, or provide a PR number/URL/branch
• To detect bugs, regressions, or security issues in changed code
• To assess architectural or flow impact of signature/type/API changes
• To validate code quality, error handling, and performance risks introduced by the PR
• When you need evidence-backed comments with exact file/line links for reviewers or maintainers

Best practices

• Provide the PR number, URL, or branch and any project-specific review guidelines before starting
• If you want a shallow scan say “Quick”; otherwise allow Full mode for safety
• Do not expect a review if Octocode MCP tools are unavailable — the check blocks progress
• Point out specific focus areas (security, performance, API compatibility) to prioritize analysis
• Supply local repo access when possible so LSP/local tools can be used for deeper traceability

Example use cases

• A maintainer asks “is this PR safe to merge?” and wants security and dependency checks
• A reviewer needs architecture impact analysis after a type or API signature change
• A team wants a checklist-style report showing failing domains (bug, performance, security) with file links
• A developer requests targeted feedback on new code paths or data transformations
• A release engineer needs evidence that changed code does not break callers or public contracts