pr-ready
Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
- Installs
- 704
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/remotion-dev/remotion --skill pr-ready- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pr-ready automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
ghCLI.
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
ghCLI. - 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.
FAQ
What does the pr-ready skill do?
Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
How do I install pr-ready?
Run npx skills add https://github.com/remotion-dev/remotion --skill pr-ready in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pr-ready/ (personal) or .claude/skills/pr-ready/ (project).
Which AI agents can use pr-ready?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pr-ready safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pr-ready?
It is published by remotion-dev in remotion-dev/remotion. It has 704 recorded installs.
More from remotion-dev/remotion
web-renderer-test
remotion-dev/remotion
Add explicitly requested web renderer tests or update existing ones for implementation changes.
writing-docs
remotion-dev/remotion
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
video-report
remotion-dev/remotion
Generate a report about a video
add-sfx
remotion-dev/remotion
Add a new sound effect to @remotion/sfx
docs-demo
remotion-dev/remotion
Add an interactive demo to the Remotion documentation. Use when creating a new component for docs pages.
add-expert
remotion-dev/remotion
Add a new expert to the Remotion experts page
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.