github-code-review

Review Git diffs and GitHub pull requests with structured feedback.

Updated May 15, 2026
One-click install
npx skills add https://github.com/cabezno/bmb-encover-agent --skill github-code-review-cabezno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill github-code-review-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you catch correctness, security, and quality issues in Git changes early by reviewing diffs locally or PRs on GitHub.

Core Features & Use Cases

  • Local pre-push reviews: Review staged or branch diffs against a target (e.g., main) using git diff and targeted checks (secrets, TODOs, conflict markers).
  • PR reviews on GitHub: Fetch PR details, view diffs, check out PR branches for full context, and leave PR comments and inline review feedback.
  • Structured output & checklist: Produce actionable feedback using a consistent Critical/Warnings/Suggestions/Looks Good format and a repeatable review workflow.

Use case: You’re about to merge a PR and want an actionable review—highlighting security risks like injection paths, pointing out missing tests, and suggesting improvements—before it reaches production.

Quick Start

Tell the agent: Review PR #123 on GitHub and leave a structured summary with inline comments where needed.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I automate code review for GitHub pull requests?

Automate GitHub pull request code review by fetching PR diffs via git, gh, or REST APIs, inspecting file context, and submitting inline comments alongside a structured Critical/Warning/Suggestion report.

Can I review local git diffs before pushing to a remote repository?

Yes, you can review local staged or branch diffs against a target like main before pushing by inspecting the git diff for secrets, TODOs, and conflict markers to catch issues early.

What is the best way to leave inline review feedback on a GitHub PR diff?

The best way to leave inline feedback is to fetch the PR details, check out the branch for full context, inspect the diff, and submit atomic inline comments through GitHub REST APIs.

Does this automated code review workflow require authenticated GitHub access?

Yes, authenticated GitHub access is required to fetch PR details, retrieve diffs, check out branches, and submit structured inline review feedback via gh or GitHub REST APIs.

How does the security checklist work during a git diff review?

The security checklist works by scanning the git diff for vulnerabilities like injection paths and exposed secrets, categorizing findings into Critical, Warning, Suggestion, or Looks Good sections.

What are the limitations of using local git diff for pre-push validation?

Local git diff validation may lack full repository context or CI integration, making it best suited for targeted checks like conflict markers and TODOs rather than end-to-end PR feedback.