crit-pr-review

Convert code-review findings into Crit-formatted inline comments for GitHub PRs.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/JonnyCBB/claude-code-config --skill crit-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crit-pr-review
Source: https://github.com/JonnyCBB/claude-code-config/tree/main/plugins/jbb-feature-dev/skills/crit-pr-review
Command: npx skills add https://github.com/JonnyCBB/claude-code-config --skill crit-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post code review findings to a GitHub PR using crit for interactive review and submission.

Core Features & Use Cases

  • Convert code-review findings into crit comments
  • Pre-populate critiques and review flow with interactive edits
  • Post inline comments or approvals to GitHub PRs programmatically
  • Handle existing reviews and re-use or regenerate review documents

Quick Start

Provide a PR number or path to an existing review document to start the Crit-powered review process.

Frequently Asked Questions about crit-pr-review

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

FAQPage Schema
How do I post code-review findings as inline comments on a GitHub pull request?

To post code-review findings as inline comments on a GitHub pull request, this Skill automates converting review documents into Crit-formatted comments and submitting them programmatically. It requires a PR number or review document path, Crit tooling, and GitHub authentication.

Can I reuse an existing review document to generate GitHub PR comments?

Yes, you can reuse an existing review document to generate GitHub PR comments. The Skill handles existing reviews by re-using or regenerating review documents, allowing you to pre-populate critiques and submit them as inline comments or approvals to GitHub.

What is the best way to automate submitting a code review with Approve or Request Changes on GitHub?

The best way to automate submitting a code review with Approve or Request Changes on GitHub is using Crit workflows. This Skill pre-populates the review flow with interactive edits and posts the final review to the PR programmatically with optional Approve or Request Changes statuses.

Do I need GitHub authentication to post code-review comments with Crit?

Yes, you need GitHub authentication to post code-review comments with Crit. Along with valid GitHub authentication, the Skill requires a specific PR number or a path to a review document and the Crit tooling to execute the interactive review and submission workflow.

How does an interactive code review workflow in Crit work before posting to GitHub?

An interactive code review workflow in Crit works by pre-populating critiques and allowing interactive edits before final submission. The Skill automates converting the findings into Crit comments, enabling you to refine the review document before posting it as inline comments to GitHub.