Pr Ready Agent Skill

by remotion-dev

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

417 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

55471

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

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

The instruction itself

as written by the author

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.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take remotion-dev/pr-ready from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.