pr-ready

Unsticks a pull request that can't be merged yet — a clash with the main branch, a failing check, or work still sitting on your own machine.

WHEN TO USE

SCOPE

USE FOR

Rebase a pull request branch onto main and resolve its merge conflicts.
Fix the underlying cause of a failing CI check instead of retrying it.
Confirm a pull request has no blockers left before reporting it ready.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

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:

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

If there is a merge conflict:

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

If there is a CI failure:

Inspect the failing check logs with the gh CLI.
Fix the underlying cause instead of retrying or bypassing the failure.
Run the relevant local checks that cover the failure.
Commit the fix if needed.
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.

Install this skill from remotion-dev/remotion on GitHub, not from a copy somewhere else. The command below does this for you.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add remotion-dev/remotion --skill "pr-ready" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

View on GitHub

No requirements beyond installing this skill were found.

More skills

fix-dependabot

issue-management