code-review-github

Analyze GitHub pull request diffs and linked issues, then publish structured findings as PR comments.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/pekral/pekral.cz --skill code-review-github-pekral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-github
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/code-review-github
Command: npx skills add https://github.com/pekral/pekral.cz --skill code-review-github-pekral

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, blader/humanizer, and includes scripts (resource) components.

What problem does it solve?

It turns GitHub pull request diffs and related linked issues into structured, actionable review findings that get published directly as PR comments and mirrored as non-technical issue summaries.

Core Features & Use Cases

  • GitHub PR code review with PR-comment publishing: Produces Critical/Moderate/Minor findings and posts them as a single upserted PR comment keyed to the actor.
  • Linked-issue consolidated summaries: For each linked issue in the PR’s closingIssues list, delegates one consolidated non-technical comment via the shared pr-summary skill.
  • Assignment compliance verification: Runs assignment compliance checks and embeds the verdict into the linked-issue summary (without posting a separate compliance-only comment).
  • Safety-first read-only workflow: Performs reviews using data loading and publishing via GitHub comment upserts, while avoiding any git write operations.

Quick Start

Use code-review-github to review a GitHub pull request by loading its context, running the required review lenses, and upserting the results into the PR and each linked issue summary.

Frequently Asked Questions about code-review-github

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

FAQPage Schema
How do I automate GitHub pull request code reviews and post the findings as a PR comment?

Automating GitHub pull request code reviews involves analyzing the PR diff and linked issues, then publishing structured Critical, Moderate, and Minor findings as a single upserted PR comment keyed to the actor. The workflow operates entirely read-only without performing any git write operations.

Can I check pull request assignment compliance and post a non-technical summary to linked issues?

Yes, you can check assignment compliance and embed the verdict into a consolidated non-technical summary. This summary is published as a single comment to each linked issue in the PR's closingIssues list without posting a separate compliance-only comment.

Does the code review process support security and refactoring analysis for GitHub PRs?

The code review process supports security and refactoring analysis by applying dedicated review lenses to the PR diff. It identifies security risks, refactoring opportunities, and DRY violations to generate actionable feedback. It also optionally checks database-operation hotspots.

Do I need to install jq and gh to run automated pull request reviews?

Yes, you need to install jq, gh, and blader/humanizer because the review workflow relies on these dependencies for deterministic context loading via scripts and PR comment upserts via gh.

What are the limitations of using a read-only workflow for GitHub code reviews?

The limitation of a read-only workflow for GitHub code reviews is that it strictly avoids any git write operations. This safety-first approach ensures the review process only loads context and upserts comments without modifying the repository state. All findings are published exclusively via comment upserts.