honest-pr-review

Reviews GitHub pull requests and posts line-anchored findings via the GitHub API.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill honest-pr-review-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: honest-pr-review
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/honest-pr-review
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill honest-pr-review-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews that only skim a diff miss the bugs that live in surrounding context, and reviews padded with vague nits waste everyone's time. This Skill makes you read the full files behind a change, verify every finding against real code, and post one consolidated GitHub review with comments anchored to exact diff lines. ## Core Features & Use Cases - Context-first review: Fetches the PR head ref and reads whole files, callers, and contracts beyond the diff hunks before forming any finding. - Verified, ranked findings: Every comment must name a concrete failure with specific inputs, and findings are split into fix-before-merge versus optional. - Correct GitHub review posting: Builds a single review JSON with commit_id, line anchors validated against the diff, and the right event (COMMENT on your own PRs, APPROVE or REQUEST_CHANGES on others), then verifies every comment landed. - Use Case: Before merging a substantial PR, ask for an honest review — you get one GitHub review where each comment cites the exact line, the concrete failure scenario, and a suggested fix, plus an explicit note on what was not verified. ## Quick Start Review PR number 42 honestly and leave a line-commented review on GitHub.

Frequently Asked Questions about honest-pr-review

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

FAQPage Schema
How do I post a GitHub PR review with line comments via the API?

Build a JSON body with the PR head SHA as commit_id, an event such as COMMENT, and a comments array where each entry has path, line, and side. POST it to repos/OWNER/REPO/pulls/NUMBER/reviews, then query the PR comments endpoint to confirm every line comment landed.

How to review a pull request beyond just reading the diff?

Fetch the PR head ref and read the full files each hunk lives in, plus the callers and the contracts of anything the change calls. Most real findings come from asking what values can actually reach a variable, which the diff alone never shows.

Why does GitHub reject my review comments with a 422 error?

A 422 usually means a comment's line is outside the diff hunks, the side is wrong, or the commit_id is not the PR head SHA. Each line must be an added or context line in the diff, and one bad anchor fails the entire review POST.

Can I approve or request changes on my own pull request?

No, GitHub rejects APPROVE and REQUEST_CHANGES events on your own PRs. Use the COMMENT event instead, which still posts the full review body and all line-anchored comments under one review.

When should I use an AI code review service instead of reviewing manually?

Use a hosted service like CodeRabbit when you want automated findings posted without reading the code yourself. Review manually when you need verified, context-aware judgment on a substantial change before merging.