pr-manager
Skill2 starsChanged 2 months agoMITView on GitHub
Manage the pull-request or merge-request lifecycle from exact repo and branch resolution through draft creation, updates, monitoring, and ready-for-review transitions, without merging or posting without authority.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- odykyi/gh-skillstheir own version, first seen Oct 25, 2026
- aiunlocked1412/claude-skill-unlocktheir own version, first seen Apr 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- aiunlocked1412/claude-skill-unlock★ 18same name
- odykyi/gh-skills★ 2same 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 repository19 other files it gives its agents.
- access-checkSkill
- babysit-prsSkill
- browser-proofSkill
- bugfixSkill
- bug-reproSkill
- cleanupSkill
- contextSkill
- dev-flowSkill
- docs-managerSkill
- hot-reloadSkill
- jira-managerSkill
- polishSkill
- release-proofSkill
- status-reportSkill
- sync-projectSkill
- watch-loopSkill
- whatsapp-meSkill
- workflowSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use this when code changes need a pull request or merge request, or when an existing review should be monitored from the terminal.
- Distinctive: line 26
Before any action, resolve:
- Distinctive: line 37
Do not guess the repo from the current shell if the task can name it explicitly.
- Distinctive: line 66
create or update the PR or MR
- Distinctive: line 67
read the saved result back
- Distinctive: line 87
Never merge from this skill without explicit authority.
- Distinctive: line 88
Never post comments or review requests without explicit authority.
- Very specific: line 89
Keep the repo/head/base exact.
- Distinctive: line 90
Do not call a branch ready just because local tests passed if required remote checks are still pending.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
PR Manager
Use this when code changes need a pull request or merge request, or when an existing review should be monitored from the terminal.
Default mode
Read-only by default.
Safe default actions:
- inspect an existing PR or MR
- resolve exact repo, head, and base
- list checks, comments, or merge state
- draft a PR body
- prepare an update or review comment preview
Creating, updating, commenting, requesting review, or merging needs explicit authority.
Resolve exact identity first
Before any action, resolve:
Hosting system
Repository
Head branch
Base branch
Current commit
Existing PR or MR number, if anyDo not guess the repo from the current shell if the task can name it explicitly.
Draft workflow
Prepare a preview with:
Action:
Repo:
Head:
Base:
Title:
Body:
Linked tickets:
Exact create or update command:The preview should include:
- problem
- root cause or change summary
- proof
- known risks or follow-up
Write workflow
Once authority is explicit:
- resolve repo, head, base, and current commit again
- create or update the PR or MR
- read the saved result back
- return the URL, state, and proof
Monitor workflow
For a watch-style use, report:
PR or MR:
Repo:
Head:
Base:
Checks:
Reviews:
Mergeability:
Next useful action:Rules
- Never merge from this skill without explicit authority.
- Never post comments or review requests without explicit authority.
- Keep the repo/head/base exact. Those identities are part of the proof.
- Do not call a branch ready just because local tests passed if required remote checks are still pending.
Stop rules
Stop when:
- the read result is complete
- the draft preview is ready
- the authorized create or update is confirmed
- the PR or MR is waiting on human review or external checks
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.

