post-review

Post saved GitHub pull request reviews with validated inline comments.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill post-review-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-review
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/post-review
Command: npx skills add https://github.com/gittower/git-flow-next --skill post-review-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a previously written local review into a properly posted GitHub pull request review, saving time and reducing the risk of formatting mistakes or missing inline feedback.

Core Features & Use Cases

  • Review File Parsing: Reads either /pr-review or /code-review formatted review files and extracts the PR number, review event, summary, and findings.
  • Inline Comment Mapping: Checks the PR diff so inline comments are only posted on lines that are actually visible in the reviewable diff.
  • Flexible Posting Controls: Supports posting by PR number or file path and can apply extra instructions such as only posting must-fix items or skipping nitpicks.
  • Use Case: A reviewer finishes a detailed code review locally and uses this Skill to publish it to GitHub with correctly placed inline comments and the right review status.

Quick Start

Use the post-review skill to post the review file for PR 92, keeping only the must-fix items.

Frequently Asked Questions about post-review

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

FAQPage Schema
How do I post local code review notes to a GitHub pull request with inline comments?

You can post local code review notes to a GitHub pull request by parsing a saved review file into structured metadata and findings, then mapping inline comments to the visible PR diff before submitting the review event.

Can I filter GitHub PR review findings by severity when publishing feedback?

Yes, you can filter GitHub PR review findings by severity when publishing feedback by applying flexible posting controls that restrict the output to only must-fix items or skip minor nitpicks.

What file formats are supported for converting local review notes into GitHub PR reviews?

Supported file formats for converting local review notes into GitHub PR reviews include files formatted with either the /pr-review or /code-review structure, which provide the PR number, review event, summary, and findings.

Why are my inline comments failing to post on the correct lines of a GitHub PR diff?

Inline comments fail to post on the correct lines of a GitHub PR diff when the target lines are not visible in the reviewable diff, requiring a validation check against the PR diff before submission.

Does this review automation approach support posting comments by file path instead of PR number?

Yes, this review automation approach supports posting comments by file path instead of PR number, allowing reviewers to map local review findings directly to files within the GitHub pull request diff.