Run any Skill in Manus with one click

Get Started

pr-ready

Stars52,943

Forks3,829

UpdatedJune 5, 2026 at 08:56

Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

remotion-dev

remotion-dev/remotion

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	pr-ready
description	Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

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 are uncommitted changes, untracked files that look relevant, or commits that have not been pushed, stop before changing, committing, or pushing them and ask the user for confirmation.

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.
Ask the user for confirmation before pushing if the conflict resolution creates unpushed commits.

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.

More from this repository

same repository

add-effect

remotion-dev/remotion

Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, tests, formatting, and builds.

2026-07-1152.9k

add-sfx

remotion-dev/remotion

Add a new sound effect to @remotion/sfx

2026-07-1152.9k

update-chrome-binaries-test-region

remotion-dev/remotion

Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.

2026-07-1152.9k

skill-locations

remotion-dev/remotion

Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.

2026-07-1052.9k

studio-css-reset

remotion-dev/remotion

Guidance for Remotion Studio UI changes where the global CSS reset affects nested elements. Use when editing packages/studio UI, especially when adding wrapper spans, inline icons, labels, buttons, compact rows, or any nested text whose typography, color, sizing, or truncation must stay stable.

2026-07-0952.9k

studio

remotion-dev/remotion

Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally.

2026-07-0952.9k

name	pr-ready
description	Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

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 are uncommitted changes, untracked files that look relevant, or commits that have not been pushed, stop before changing, committing, or pushing them and ask the user for confirmation.

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.
Ask the user for confirmation before pushing if the conflict resolution creates unpushed commits.

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.