review-pr

Original：🇺🇸 English

Translated

Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.

14installs

Sourcefreekmurze/dotfiles

Added on2026-02-28

NPX Install

npx skill4agent add freekmurze/dotfiles review-pr

SKILL.md Content

View Translation Comparison →

Review PR

Review a GitHub pull request, verify CI status, and merge + tag a release if appropriate.

Workflow

1. Fetch PR details

Use

gh

CLI to get the PR diff, description, and CI status:

bash

gh pr view <number> --json title,body,additions,deletions,files,reviews,statusCheckRollup,headRefName,baseRefName
gh pr diff <number>

2. Review the changes

Carefully review the diff. Pay attention to:

Code quality and correctness
Potential bugs or edge cases
Whether the change matches the PR description
Test coverage for new functionality
Adherence to existing code style and patterns in the package

If there are issues, post a review comment via

gh pr review <number> --request-changes --body "..."

and stop.

3. Check CI status

All CI checks must be green before merging. Verify via the

statusCheckRollup

field from step 1. If CI is failing or pending, inform the user and stop.

4. Merge and release

If the review looks good and CI is green:

Merge the PR:

gh pr merge <number> --squash --delete-branch

Determine the appropriate version bump by checking the latest tag:
```
gh release list --limit 1
```
Tag a new release with the next appropriate version number

Versioning rules

NEVER tag a major version bump without explicit user approval. Always ask first.
Dropping support for a PHP or Laravel version is NOT a breaking change — use a minor or patch bump.
New features: minor version bump (e.g. 1.2.0 → 1.3.0)
Bug fixes, typos, dependency updates: patch version bump (e.g. 1.2.0 → 1.2.1)
When in doubt about the version bump level, ask the user.

Creating the release