Verified:GitHub

cocosearch-review-pr

Fetch GitHub and GitLab PR diffs and metadata for structured review analysis.

37|6|Updated Feb 16, 2026

Search Tags:#github #gitlab #code-review #tests #blast-radius #pr-review #dependency-analysis

One-click install

npx skills add https://github.com/VioletCranberry/coco-search --skill cocosearch-review-pr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cocosearch-review-pr
Source: https://github.com/VioletCranberry/coco-search/tree/main/skills/cocosearch-review-pr
Command: npx skills add https://github.com/VioletCranberry/coco-search --skill cocosearch-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews can be time-consuming and error-prone when evaluating diffs, metadata, and impact; this skill automates the process by fetching data from hosting platforms and generating structured analysis.

Core Features & Use Cases

Fetches PR/MR metadata and diffs from GitHub and GitLab via API tokens.
Performs blast-radius analysis, dependency impact, pattern consistency, and test coverage checks.
Produces per-file findings and cross-cutting insights to guide review decisions.
Use case: quickly assess risk in a 50+ file PR by focusing on high-impact files and missing tests.

Quick Start

Paste the PR or MR URL to start the review and make sure the appropriate API tokens are configured.

Frequently Asked Questions about cocosearch-review-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitHub PR review with blast radius analysis?▼

Automate GitHub PR review by pasting the pull request URL to fetch diffs and metadata via API tokens, generating structured per-file findings and cross-cutting blast radius insights. This assesses dependency impact, pattern consistency, and test coverage for high-risk files.

What is blast radius analysis in code review?▼

Blast radius analysis in code review evaluates the dependency impact and cross-cutting concerns of changed files to determine how far-reaching the effects of a PR are. It highlights high-impact files and missing tests to guide review decisions and prioritize risk assessment.

Can I review GitLab merge requests using a URL?▼

Yes, you can review GitLab merge requests by pasting the MR URL. The skill fetches diffs and metadata using configured API tokens, applying blast radius, dependency impact, pattern consistency, and test coverage assessments to produce structured review findings.

Do I need API tokens to analyze pull request dependencies?▼

Yes, you need configured API tokens for GitHub or GitLab to fetch PR or MR metadata and diffs. Token-based access is required to retrieve the code changes necessary for performing dependency analysis and generating structured review outputs.

What's the best way to assess test coverage in large pull requests?▼

Assess test coverage in large pull requests by fetching the diff via URL and analyzing the structured per-file findings. The review identifies missing tests and highlights high-impact files, allowing you to focus on critical areas within 50+ file PRs.

Are there limitations when reviewing PRs for pattern consistency?▼

Pattern consistency review depends on the fetched diffs and metadata from the hosting platform. It is limited by the configured API token permissions and works best when analyzing the generated structured outputs for per-file findings and cross-cutting concerns across the submitted changes.