finalize-pr
Skill31 starsChanged 6 months agoMITView on GitHub
Orchestrates the full post-implementation loop: push PR → wait for CI → fix failures → repeat until CI passes or termination rules trigger a pause. This skill should be used when the user says "ship it", "finalize pr", "push and fix CI", "push pr and wait for CI", or invokes "codagent:finalize-pr".
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the independently reusable PR skills to make the current branch review-ready:
- Distinctive: line 31
When pausing, include the current CI or review evidence and the attempted fixes.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Finalize PR
Use the independently reusable PR skills to make the current branch review-ready:
- Invoke
codagent:push-pr. - Invoke
codagent:wait-ci. - On
failedorcomments, invokecodagent:fix-pr, then return to waiting. - On
passed, report success and the PR URL.
For pending, report what remains and ask whether to wait longer.
Termination
Track each fix cycle's failure signature: the set of failing check names, or comments-only when only
review feedback remains.
Pause for user direction instead of fixing when:
- three fix cycles have already run; or
- the same signature remains after two consecutive fix attempts.
When pausing, include the current CI or review evidence and the attempted fixes. Do not archive changes; archiving is a separate operation.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- microsoft/bocpy★ 184same name
- microsoft/rego-cpp★ 48same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- releaseSkill
- releaseSkill
- ask-questionsSkill
- call-agentSkill
- designSkill
- fix-prSkill
- handoffSkill
- implement-changeSkill
- initSkill
- orchestrate-changeSkill
- plan-tasksSkill
- prepare-acceptanceSkill
- proposal-reviewSkill
- proposeSkill
- push-prSkill
- review-approachSkill
- review-assumptionsSkill
- review-specSkill
- review-tasksSkill
- session-reportSkill
- simple-planSkill
- specSkill
- task-complianceSkill
- test-flowsSkill
- test-planSkill
- verify-behaviorSkill
- wait-ciSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.