github-code-review

Review local git changes and GitHub pull requests with inline comments via gh or REST API.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill github-code-review-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill github-code-review-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code before pushing or evaluating open pull requests requires juggling diffs, context, and GitHub's review APIs manually, which is slow and error-prone. This Skill provides a structured workflow for pre-push reviews and end-to-end PR reviews with inline comments and formal verdicts. ## Core Features & Use Cases - Pre-Push Local Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, conflict markers, and oversized files. - Full PR Review Workflow: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit an atomic review with inline comments via gh or the GitHub REST API. - Structured Feedback Format: Present findings as Critical / Warnings / Suggestions / Looks Good, with a reusable output template and severity guide. - Use Case: A teammate opens PR #123 touching auth code. You ask the agent to review it; it checks out the branch, runs the test suite, flags a SQL injection at src/auth.py:45, and posts a REQUEST_CHANGES review with inline comments and a summary comment. ## Quick Start Ask the agent to review PR number 123 in the current repository and post inline comments with a summary verdict.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I review a GitHub pull request from the command line?▼

Fetch the PR branch with git fetch origin pull/123/head:pr-123 and check it out, then inspect the diff with git diff main...HEAD. Use gh pr view and gh pr diff for metadata, and submit feedback with gh pr review or the REST API reviews endpoint.

How to add inline comments to a GitHub PR via API?▼

POST to /repos/{owner}/{repo}/pulls/{number}/comments with the body, file path, head commit SHA, line number, and side. You can also submit multiple inline comments atomically through the /reviews endpoint with an event of APPROVE, REQUEST_CHANGES, or COMMENT.

Can I review code without the gh CLI installed?▼

Yes, local pre-push reviews use plain git commands like git diff main...HEAD with no API access. For PR interactions, the Skill falls back to curl with a GITHUB_TOKEN read from the environment, a .env file, or git credentials.

What should I check in a code review before pushing?▼

Check correctness, security issues like hardcoded secrets or SQL injection, code quality, test coverage, performance problems like N+1 queries, and documentation. Grep the diff for leftover debug statements, TODOs, and merge conflict markers.

When should I request changes versus approve a pull request?▼

Approve when there are no critical or warning-level issues, only minor suggestions. Request changes when any critical issue like a security vulnerability or warning like missing error handling exists. Use comment-only reviews for draft PRs or uncertain findings.