giving-code-review

Reviews pull requests via gh by walking every commit and verifying claims before posting findings.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill giving-code-review-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: giving-code-review
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/giving-code-review
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill giving-code-review-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests thoroughly is hard: reviewers skim diffs, trust unverified claims like "tested locally", miss prior review threads, and rubber-stamp their own PRs. This Skill provides a structured reviewer-side workflow that catches what casual re-reads miss. ## Core Features & Use Cases - Self vs external review detection: Compares the PR author with your GitHub identity via gh to choose self-review or external-review mode, applying doubled rigor to your own code. - Full commit-range walkthrough: Reviews every commit oldest-first, flags mixed concerns, net-zero changes, and misleading commit messages, and recommends splitting oversized PRs instead of partial reviews. - Trust-but-verify pass: Treats every claim in PR descriptions and prior comments as unproven, constructing minimal falsifying inputs and checking backward compatibility for callers on old behavior. - Use Case: A teammate opens a 12-commit PR claiming a race condition fix. Use this Skill to walk each commit, build the adversarial case against the fix, check prior review threads for unaddressed feedback, and post one atomic inline review via the GitHub API. ## Quick Start Ask the AI to review pull request number 42 in the current repository using the giving-code-review workflow and show the findings before posting.

Frequently Asked Questions about giving-code-review

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

FAQPage Schema
How do I review a pull request using the gh CLI?

Use gh pr view to fetch the PR metadata and commits, then git log over the branch range to walk every commit oldest-first. Post findings as one atomic review with inline comments via gh api repos/{owner}/{repo}/pulls/<number>/reviews.

How to review my own pull request before requesting external review?

Self-review mode checks out and runs the code rather than eyeballing the diff, reviews after a context switch, and re-derives adversarial cases against your own claims. Leave inline self-comments on non-obvious changes to prime the next reviewer.

What should I check when reviewing a large pull request?

If the range exceeds roughly 30 commits or 1000 changed lines, say so up front and recommend splitting the PR rather than rushing a partial pass. A review that skips commits to fit a budget is worse than an honest request to split.

Does this review workflow work outside this harness repository?

Yes. In this repo with a spec attached it dispatches the pr-reviewer agent, but for any other repo you walk the diff yourself against the same dimensions: code quality, docs, security, reliability, performance, and adversarial edge cases.

How should I handle prior review comments on a pull request?

Fetch prior comments with gh api and flag adverse advice that would make the PR worse, amplify good unaddressed suggestions, and cite existing comments instead of re-raising already-caught issues. Silence on bad advice reads as agreement.