Fastlane Pull Request Review
fastlane/fastlane
Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.
Reviews a GitHub pull request against the ruby-git project standards, shows findings first, and posts review comments with the gh CLI only after you approve.
Install Pull Request Review Workflow
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ruby-git/ruby-git pull-request-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/pull-request-review .claude/skills/pull-request-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .claude/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ruby-git/ruby-git pull-request-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/pull-request-review .agents/skills/pull-request-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .agents/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ruby-git/ruby-git pull-request-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/pull-request-review .cursor/skills/pull-request-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .cursor/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ruby-git/ruby-git.git --path .github/skills/pull-request-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ruby-git/ruby-git pull-request-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/pull-request-review .gemini/skills/pull-request-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .gemini/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ruby-git/ruby-git pull-request-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/pull-request-review .github/skills/pull-request-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .github/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruby-git/ruby-git --skill pull-request-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ruby-git/ruby-git pull-request-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/pull-request-review .opencode/skills/pull-request-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pull-request-review" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/pull-request-review into .opencode/skills/pull-request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pull-request-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pull-request-review- GitHub stars
- 1.8k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 638 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews a GitHub pull request against the ruby-git project standards, shows findings first, and posts review comments with the gh CLI only after you approve.
- Works in 6 steps: Fetch the PR → Review Against Project Standards → Present Review Findings → …
- Reviewing a pull request before approving it
- SKILL.md covers Contents, How to use this skill, Related skills and Step 1: Fetch the PR, plus 5 more sections
- Calls gh
What it does
Given a request to review a specific PR number, the agent fetches the pull request with gh pr view and gh pr diff, noting draft status, merge conflicts and existing reviews. It then checks the change against project criteria: RuboCop-compliant Ruby style, frozen string literal comments, naming, single responsibility, no duplication, Ruby 3.3 idioms, and atomic, well-named RSpec specs with passing CI.
Findings are shown to you before anything is posted. The workflow has an explicit approval step, so no review comments reach GitHub until you confirm, and it ends with a completion check. Related skills cover RSpec standards, pre-PR readiness reviews, CI troubleshooting and backward-compatibility audits. The skill is written to be attached to Copilot Chat context.
When your agent uses it
- Reviewing a pull request before approving it
- Checking a PR for RuboCop, naming and RSpec compliance
- Preparing review comments to post through the gh CLI
- Doing an approval review that you confirm before posting
Example prompts
- “Review PR #999 against our project standards.”
- “Check whether this pull request's specs are atomic and well named, then show me the findings.”
- “Post the approved review comments on PR #999.”
Requirements
- The GitHub CLI (gh), authenticated for the repository
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f3bf20f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pull Request Review Workflow loads about 1.6k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 638 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ruby-git/ruby-git at commit f3bf20f, republished under its MIT licence (© ruby-git). 638 words, ~1,590 tokens.
Download SKILL.mdSave it as
.claude/skills/pull-request-review/SKILL.md (or your agent's skills folder).- name
- pull-request-review
- description
- Reviews pull requests against project standards and posts review comments via the gh CLI. Use when reviewing PRs, checking coding standards compliance, or performing approval reviews.
Pull Request Review Workflow
When asked to review a pull request (e.g., "Review PR #999"), follow this workflow to analyze the changes, provide feedback, and optionally post the review to GitHub.
Contents
- How to use this skill
- Related skills
- Step 1: Fetch the PR
- Step 2: Review Against Project Standards
- Step 3: Present Review Findings
- Step 4: Get User Approval
- Step 5: Post the Review
- Step 6: Confirm Completion
How to use this skill
Attach this file to your Copilot Chat context, then invoke it with the PR number to review. Follow Step 4 explicitly: do not post review comments until the user confirms.
Related skills
- RSpec Unit Testing Standards — RSpec rules to apply when evaluating test quality in a PR
- PR Readiness Review — internal pre-PR checks before formal review
- CI/CD Troubleshooting — investigate failed checks discovered during review
- Review Backward Compatibility — deeper audit when API compatibility concerns surface
Step 1: Fetch the PR
- Read PR Details: Use
gh pr view #999to get title, description, author, and status. - Get Changed Files: Use
gh pr diff #999to see the complete diff. - Check PR Status: Note if it's a draft, has merge conflicts, or has existing reviews.
Step 2: Review Against Project Standards
Evaluate the PR against these criteria:
Code Quality: Ruby style (RuboCop-compliant), frozen_string_literal: true, proper naming (snake_case/PascalCase), single-responsibility, no duplication, Ruby 3.3+ idioms.
Testing: Changes are covered by atomic RSpec specs (spec/), well-named, and passing CI.
Documentation: YARD docs on public methods with @param, @return, @raise, @example. README updated for user-facing changes. Platform differences and security documented. For Git::Commands::* classes, @raise [Git::FailedError] must use the canonical generic wording — never enumerate failure causes; see the @raise wording table in Command YARD Documentation.
Architecture: Correct layer placement (Base/Lib/CommandLine), principle of least surprise, direct Git command mapping, proper error hierarchy.
Commits: Conventional Commits format, lowercase subjects under 100 chars, no trailing period. Breaking changes use ! and BREAKING CHANGE: footer.
Compatibility: Backward compatible (or marked breaking), Ruby 3.3+, Git 2.43.0+, cross-platform (Windows/macOS/Linux).
Security: No command injection, proper escaping via Git::CommandLine, input validation, resource cleanup. Before flagging a missing cleanup or restore on a failure path, check the method's @note and docs/adr/: ADR-0009 decides what a failed operation leaves behind, and some methods leave state behind on purpose.
Show full SKILL.md (261 more words)Show less
Step 3: Present Review Findings
Present your findings to the user in this format:
# PR Review: #999 - [PR Title]
**Author:** [username]
**Status:** [open/draft/has conflicts/etc.]
## Summary
[Brief description of what the PR does]
## Recommendation
- **Review Type:** [APPROVE / COMMENT / REQUEST CHANGES]
- **Rationale:** [Why this recommendation]
## General Comments
[Overall feedback on the PR - architecture decisions, approach, etc.]
## Line-Specific Comments
[file.rb:123]
[Specific feedback about this line or section]
[file.rb:456-460]
[Feedback about this range of lines]
## Checklist Results
**Passing:**
- Uses proper Ruby style
- Tests included
- ...
**Issues Found:**
- Missing YARD documentation on `SomeClass#method`
- Commit message "Fixed bug" doesn't follow conventional commits
- ...
---
**Here is the review. Do you have any questions or want additional changes, OR should I go ahead and post this review on the PR?**Step 4: Get User Approval
Wait for the user to respond. They may:
- Approve posting: Proceed to Step 5
- Request changes to review: Modify your findings and re-present
- Ask questions: Answer and clarify before proceeding
- Decide not to post: End the workflow
Do NOT post the review without explicit user confirmation.
Step 5: Post the Review
Once the user confirms, post the review using the GitHub CLI:
For reviews with line-specific comments:
- Create the review:
gh pr review #999 --comment(or--approveor--request-changes) - Add the general comment as the review body using
-b "comment text" - For line-specific comments, you may need to use the GitHub API or instruct the user to add them manually in the GitHub UI
For reviews with only general comments:
gh pr review #999 --approve -b "Your general comment here"
# or
gh pr review #999 --comment -b "Your general comment here"
# or
gh pr review #999 --request-changes -b "Your general comment here"Note: The gh CLI has limitations with line-specific comments. If the review
includes line-specific comments, inform the user of this limitation and either:
- Post only the general comment via CLI and provide the line comments for manual posting
- Provide the full review text for the user to post manually
- Use the GitHub API if line-specific commenting is critical
Step 6: Confirm Completion
After posting, confirm with the user:
Review posted successfully to PR #999.
View at: [PR URL from gh pr view output]When editing a PR description as part of follow-up review changes, use a file-based flow for reliability:
- write/update markdown in a local file
- run
gh pr edit #999 --body-file <path> - verify the final stored body with
gh pr view #999 --json body
Avoid long multiline inline --body "..." commands for complex markdown.
© ruby-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/pull-request-review of ruby-git/ruby-git.
Open the folder on GitHubat commit f3bf20f
Compare with similar skills
Pull Request Review Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pull Request Review Workflow this skillruby-git/ruby-git | 1.8k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Fastlane Pull Request Reviewfastlane/fastlane | 42k | — | ~550 | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
- Official
PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Pull Request Reviewer for daisyUI
saadeghi/daisyui
Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.
More from ruby-git/ruby-git
All 30 skills in this repoAddress PR Feedback for ruby-git
ruby-git/ruby-git
Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
CI/CD Failure Troubleshooting
ruby-git/ruby-git
Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.
Git Command Class Implementation
ruby-git/ruby-git
Scaffolds and reviews `Git::Commands::*` classes in the ruby-git library, with unit tests, integration tests and YARD docs, using the Base command architecture.
Gem Dependency Management
ruby-git/ruby-git
Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.
Extract Command from Git::Lib
ruby-git/ruby-git
Migrates a direct command call in Ruby Git's Git::Lib to a Git::Commands class, as part of a Strangler Fig redesign, with a plan, legacy tests and a pull request.
Related
Categories
Questions about Pull Request Review Workflow
What does Pull Request Review Workflow do?
Reviews a GitHub pull request against the ruby-git project standards, shows findings first, and posts review comments with the gh CLI only after you approve. Given a request to review a specific PR number, the agent fetches the pull request with gh pr view and gh pr diff, noting draft status, merge conflicts and existing reviews.3 idioms, and atomic, well-named RSpec specs with passing CI.
When should I use Pull Request Review Workflow?
Pull Request Review Workflow fits situations like: reviewing a pull request before approving it; checking a PR for RuboCop, naming and RSpec compliance; preparing review comments to post through the gh CLI; doing an approval review that you confirm before posting.
How do I install Pull Request Review Workflow in Claude Code?
Run `npx skills add ruby-git/ruby-git --skill pull-request-review -a claude-code`. Or copy the skill folder (.github/skills/pull-request-review in ruby-git/ruby-git) into .claude/skills/pull-request-review in your project. Claude Code loads it when a task matches its description.
How do I install Pull Request Review Workflow in Codex?
Run `npx skills add ruby-git/ruby-git --skill pull-request-review -a codex`. Or copy the skill folder (.github/skills/pull-request-review in ruby-git/ruby-git) into .agents/skills/pull-request-review in your project. Codex loads it when a task matches its description.
Can I use Pull Request Review Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruby-git/ruby-git --skill pull-request-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pull-request-review, .gemini/skills/pull-request-review, .github/skills/pull-request-review and .opencode/skills/pull-request-review in your project.
What does Pull Request Review Workflow need to run?
Going by SKILL.md and its folder, Pull Request Review Workflow needs the command-line tools its instructions call (gh). Our summary lists: The GitHub CLI (gh), authenticated for the repository.
Does Pull Request Review Workflow access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pull Request Review Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pull Request Review Workflow use?
Pull Request Review Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pull Request Review Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pull Request Review Workflow?
Skills that share tags, products or a category with Pull Request Review Workflow: Fastlane Pull Request Review (fastlane/fastlane, 42k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pull Request Review Workflow?
ruby-git (a GitHub organization) maintains it in ruby-git/ruby-git, which has 1,799 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 2, 2026.
Source: ruby-git/ruby-git on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.