review

Trigger GitHub PR reviews by posting a comment and verify workflow runs.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill review-skaisser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/skaisser/blueprint/tree/main/skills/review
Command: npx skills add https://github.com/skaisser/blueprint --skill review-skaisser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables automated PR reviews by triggering Claude's review workflow when you mention it in PR comments or use /review, ensuring consistent review triggers without manual CI actions.

Core Features & Use Cases

  • Trigger PR review on a pull request by mentioning @claude or using /review.
  • Verify that the associated GitHub Action workflow was triggered and report the status.
  • Do not modify code files; only post a triggering comment to start the CI-based review.

Quick Start

Trigger the automated PR review by mentioning /review or @claude in the pull request comment.

Frequently Asked Questions about review

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

FAQPage Schema
How do I trigger an automated PR review on GitHub using a comment?

Trigger an automated PR review by mentioning @claude or using the /review command in a pull request comment. This posts a triggering comment that initiates the CI-based review workflow without modifying code files.

What is the mechanism for starting code reviews via GitHub Actions?

The mechanism works by posting a trigger comment to the pull request, which initiates the associated GitHub Action workflow. It reads the PR number from arguments or gh pr view, then verifies that the GitHub Action runs were successfully initiated.

Can I use this to run code reviews on ongoing pull requests across CI workflows?

Yes, you can initiate code reviews across ongoing PRs and CI workflows. It automates triggering Claude's review workflow when you mention it in PR comments, ensuring consistent review triggers without manual CI actions.

Does triggering a PR review modify my code files in the repository?

No, triggering a PR review does not modify code files. It only posts a triggering comment to start the CI-based review workflow and verifies that the associated GitHub Action was triggered.

How do I verify that a GitHub Action workflow was triggered for a pull request?

After posting the trigger comment, the process verifies that the GitHub Action runs were initiated and reports the status. It reads the PR number from arguments or gh pr view to track the workflow execution.