Gh pr
Portable agent workflow framework for Codex, Claude Code, and OpenCode—shared project context, focused skills, independent review, and safe updates.
npx -y skills add K95M65/AI_ONBOARD --skill gh-prAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create or update a GitHub pull request with the gh CLI. Use when opening a PR from the current branch or updating an existing one. Pairs with the pr-description skill for the body.
SKILL.md
1.1 KB, 247 tokens by cl100k_base, as published. Nobody here has run it
GitHub PR
When to use
Opening or updating a pull request from the command line.
Steps
- Push the branch:
git push -u origin HEAD. - Write the body with the
pr-descriptionskill (save it toPR.md). - Create the PR:
gh pr create --base main --title "<title>" --body-file PR.md- Draft: add
--draft. Request review:--reviewer <user>. Self-assign:--assignee @me. - Fill fields interactively instead:
gh pr create --web.
- Draft: add
- Update an existing PR:
gh pr edit --title <t> --body-file PR.md, or just push more commits — the PR tracks the branch. - Check status:
gh pr checks(CI) andgh pr view --web.
Notes
- One logical change per PR — if the diff spans unrelated work, split it.
- Don't force-push a shared PR branch without coordinating with reviewers.
- Put
Closes #<n>in the body to auto-close the linked issue on merge.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.