Pr Ready
- 384 installs
- 55.5k repo stars
- Updated August 4, 2026
- remotion-dev/remotion
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.
About
Pr-ready is a Remotion repository workflow skill for solo builders and contributors whose pull request is stuck. It applies when CI is red, the branch conflicts with the base, or the working tree has unpushed or uncommitted work that blocks a clean review. The agent starts with git status, unpushed commit detection, conflict checks against the base branch, and GitHub CLI inspection of PR checks. For conflicts it updates the base reference, rebases or merges following existing project practice, resolves files carefully, runs formatting and tests for affected packages, and seeks confirmation before push. For CI failures it reads failing job logs via gh, fixes the underlying issue, runs the matching local verification, commits if needed, and again confirms before pushing. The skill explicitly stops for user approval whenever local changes or conflict resolution would create new commits or pushes, which keeps indie operators in control of their branch history while still automating the diagnostic steps.
- 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
Pr Ready by the numbers
- 384 all-time installs (skills.sh)
- +61 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #121 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/remotion-dev/remotion --skill pr-readyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 384 |
|---|---|
| repo stars | ★ 55.5k |
| Last updated | August 4, 2026 |
| Repository | remotion-dev/remotion ↗ |
What it does
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.
Files
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.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148