mcpField
P
pr-ready

pr-ready

github.com/remotion-devDevelopment68.6k719 installsUpdated today
Repository

About pr-ready

A repository skill for bringing a pull request back to a ready state when CI fails, conflicts occur, or changes remain uncommitted or unpushed. It guides checks, fixes, and validation while requiring confirmation before pushing newly created commits.

Key features

  1. 01Check branch and working tree status
  2. 02Review unpushed commits and merge conflicts
  3. 03Inspect CI checks with `gh`
  4. 04Resolve conflicts and fix failures
  5. 05Run relevant formatting, tests, or builds
  6. 06Request confirmation before pushing new commits

Use cases

  1. 01Diagnosing a PR blocked by CI failure
  2. 02Resolving conflicts with the base branch
  3. 03Preparing a PR with unpushed changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/remotion-dev/remotion --skill pr-ready

After installing, type/pr-readyin Claude Code to confirm it loaded.

Details

From the project README

Use this skill when a pull request is not ready because there is either:

  • a CI failure
  • a merge conflict
  • uncommitted or unpushed changes

Bring the pull request back to a ready state.

Start by checking:

  1. The current git branch and working tree state with git status.
  2. Whether the local branch has commits that are not pushed yet.
  3. Whether the PR branch has merge conflicts with the base branch.
  4. The current PR checks or CI failures using the gh CLI.

If there is a merge conflict:

  1. Update the local base branch reference.
  2. Rebase or merge the PR branch onto the base branch, following the repository's existing workflow.
  3. Resolve conflicts carefully and preserve both the PR intent and upstream changes.
  4. Run the relevant formatting, tests, or builds for the affected packages.

If there is a CI failure:

  1. Inspect the failing check logs with the gh CLI.
  2. Fix the underlying cause instead of retrying or bypassing the failure.
  3. Run the relevant local checks that cover the failure.
  4. Commit the fix if needed.
  5. Ask the user for confirmation before pushing if this creates unpushed commits.

If there are no CI failures, no merge conflicts, and no uncommitted or unpushed changes, report that the PR is already ready.

Comments

Markdown supported