Get a pull request ready by checking automated checks, merge conflicts, and local changes. Investigate failures, fix their causes, resolve conflicts, and run relevant local checks, with confirmation before pushing newly created commits.
Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
Review the instructions the agent will receive before you install.
Use this skill when a pull request is not ready because there is either:
Bring the pull request back to a ready state.
Start by checking:
git status.gh CLI.If there is a merge conflict:
If there is a CI failure:
gh CLI.If there are no CI failures, no merge conflicts, and no uncommitted or unpushed changes, report that the PR is already ready.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.