Resolve CI failures, merge conflicts, or local branch changes to get a PR ready
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
remotion-dev/remotion
cc7879e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.