submit-github-review

Publishes code review findings to a GitHub pull request via the GitHub API.

8|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill submit-github-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-github-review
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/submit-github-review
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill submit-github-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reliable way to publish code review findings directly to a GitHub pull request, ensuring consistent, auditable reviews and faster collaboration.

Core Features & Use Cases

  • Format: Transform aggregated findings into a GitHub pull request review body with inline comments.
  • Submit: Post the review to the PR via the GitHub API.
  • Annotate: Attach inline comments to specific files/lines for precise feedback.
  • Use Case: After running specialist reviews, publish the verdict on a PR to accelerate review cycles while preserving the evidence of issues.

Quick Start

Use the submit-github-review skill to post a prepared review to a PR by providing owner, repo, pull_number, commit_id, and findings.

Frequently Asked Questions about submit-github-review

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

FAQPage Schema
How do I post code review findings to a GitHub pull request via API?

To post code review findings to a GitHub pull request, provide the owner, repo, pull_number, commit_id, and findings data. The skill uses the GitHub API to submit the review and returns a review_id with a review_url.

Can I submit inline comments to specific files and lines in a GitHub PR review?

Yes, you can attach inline comments to specific files and lines in a GitHub PR review. The skill formats aggregated findings into a review body with inline comments for precise feedback annotation.

What GitHub review events are supported when submitting a pull request review?

Supported GitHub pull request review events include APPROVE, REQUEST_CHANGES, and COMMENT. You select the appropriate event when submitting findings to post the verdict via the GitHub API.

What information do I need to publish a review to a GitHub PR?

You need the repository owner, repo name, pull_number, commit_id, and the prepared findings to publish a review to a GitHub PR. These parameters allow the GitHub MCP tool to create the pull request review.

Does this code review submission tool work within an automated pipeline?

Yes, this code review submission tool operates within a code-review pipeline. After specialist reviews run, it publishes the verdict and evidence of issues to a PR to accelerate review cycles.