Pr Ready
Unblock a Remotion (or similar) pull request by fixing CI failures, resolving merge conflicts, and aligning local commits with what should ship—without silent pushes.
Install
npx skills add https://github.com/remotion-dev/remotion --skill pr-readyWhat is this skill?
- Structured triage: git status, unpushed commits, merge conflicts, and gh PR checks
- Merge conflict workflow: update base, rebase or merge per repo convention, preserve PR intent
- CI failure workflow: inspect gh logs, fix root cause, run local checks—no blind retries
- Hard gate: ask user before committing, pushing, or acting on unpushed or uncommitted work
Adoption & trust: 26 installs on skills.sh; 49.4k GitHub stars.
Recommended Skills
Triagemattpocock/skills
Caveman Commitjuliusbrussee/caveman
Using Git Worktreesobra/superpowers
Finishing A Development Branchobra/superpowers
Git Commitgithub/awesome-copilot
Git Guardrails Claude Codemattpocock/skills
Journey fit
Primary fit
Canonical shelf is Ship because the skill exists to restore PR readiness when checks fail or the branch diverges from base before merge. Review subphase matches git status triage, conflict resolution, and CI log analysis before approval.
SKILL.md
READMESKILL.md - 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: 1. The current git branch and working tree state with `git status`. 2. Whether the local branch has commits that are not pushed yet. 3. Whether the PR branch has merge conflicts with the base branch. 4. 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: 1. Update the local base branch reference. 2. Rebase or merge the PR branch onto the base branch, following the repository's existing workflow. 3. Resolve conflicts carefully and preserve both the PR intent and upstream changes. 4. Run the relevant formatting, tests, or builds for the affected packages. 5. Ask the user for confirmation before pushing if the conflict resolution creates unpushed commits. If there is a CI failure: 1. Inspect the failing check logs with the `gh` CLI. 2. Fix the underlying cause instead of retrying or bypassing the failure. 3. Run the relevant local checks that cover the failure. 4. Commit the fix if needed. 5. 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.