review-validation

Validate unresolved PR review claims against actual code with evidence.

1|1|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/jiyeol-lee/dotfiles --skill review-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-validation
Source: https://github.com/jiyeol-lee/dotfiles/tree/main/.opencode/skills/review-validation
Command: npx skills add https://github.com/jiyeol-lee/dotfiles --skill review-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validates PR review comments against actual code by analyzing reviewer claims to determine if they are valid or invalid.

Core Features & Use Cases

  • Unresolved review thread analysis to verify claims
  • Evidence-backed verdicts with confidence levels
  • Report generation with links to PR comments

Quick Start

Provide the PR number or URL and request validation of unresolved review threads against the code.

Frequently Asked Questions about review-validation

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

FAQPage Schema
How do I validate unresolved PR review threads against the actual code?

To validate unresolved PR review threads, provide the pull request number or URL and file contents. The system analyzes reviewer claims across multiple files and lines, comparing feedback against actual code behavior to produce structured verdicts with evidence.

What is the best way to verify if pull request review comments are actually valid?

Verifying pull request review comments requires analyzing claims against code truth. This process checks whether reviewer feedback matches actual code behavior across referenced files and lines, generating evidence-backed verdicts with confidence levels.

Can I automatically check code review claims across multiple files in a pull request?

Yes, you can automatically check code review claims across multiple files. By supplying pull request data and file URLs, the tool resolves unresolved threads and enforces structured verdicts to determine if feedback is valid or invalid.

Do I need to provide file contents and URLs to analyze unresolved review threads?

Yes, you need to provide file contents and pull request URLs to analyze unresolved review threads. Access to actual code and PR data is required to confirm whether reviewer feedback matches code behavior and to generate evidence-backed verdicts.

How does code analysis determine the confidence level of a review verdict?

Code analysis determines the confidence level of a review verdict by comparing reviewer claims against actual code truth. It generates evidence-backed reports with links to PR comments, structuring the output with clear validation results.