dev-pr skill
✓ VerifiedPublishes a feature branch for code review by syncing, rebasing, and opening a pull request or merge request on Git hosts.
- GitHub stars
- 1,663
- Files
- 2
- Last commit
- Nov 9, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the dev-pr skill do?
dev-pr publishes a feature branch for code review by syncing, rebasing, and opening a pull request or merge request on Git hosts.
Summary generated from the skill's SKILL.md.
About the dev-pr skill
Developers preparing to submit code for peer review can use this tool to automate the final stages of the feature branch lifecycle. It handles the technical heavy lifting of syncing local work with remote repositories by fetching updates, rebasing the current branch onto the base branch, and resolving conflicts. The skill is designed to be used after a user has already completed their commit workflow, as it will stop and request manual commits if uncommitted changes are detected.
Once the branch is synchronized and validated, the skill pushes the code to GitHub, GitLab, or other Git hosts using appropriate methods like --force-with-lease when a rebase has rewritten history. It then opens a new pull request or merge request, or updates an existing one, using tools like gh, glab, or forge CLI. The process concludes by providing a detailed report containing the review URL, the HEAD SHA, validation results, and a summary of any identified risks.
What an agent can do with it
- 1Publish a new feature branchOpen a pull request on GitHub after rebasing a local branch onto the latest main branch.
- 2Update an existing code reviewSync a feature branch with the remote base and update an active merge request.
- 3Handle rebased branch pushesPush a branch that has been rewritten via rebase using safe force-pushing techniques.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the dev-pr skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the dev-pr skill in Claude Code
~/.claude/skills/dev-pr/SKILL.md
$ npx degit codeaholicguy/ai-devkit/skills/dev-pr ~/.claude/skills/dev-prInstall the dev-pr skill in Claude Code (project)
.claude/skills/dev-pr/SKILL.md
$ npx degit codeaholicguy/ai-devkit/skills/dev-pr .claude/skills/dev-prInstall the dev-pr skill in Codex
~/.agents/skills/dev-pr/SKILL.md
$ npx degit codeaholicguy/ai-devkit/skills/dev-pr ~/.agents/skills/dev-prInstall the dev-pr skill in Gemini CLI
~/.gemini/skills/dev-pr/SKILL.md
$ npx degit codeaholicguy/ai-devkit/skills/dev-pr ~/.gemini/skills/dev-prInstall the dev-pr skill in Claude.ai
npx degit codeaholicguy/ai-devkit/skills/dev-pr dev-pr && zip -r dev-pr.zip dev-pr # claude.ai → Customize → Skills → + → Create skill → Upload a skill → dev-pr.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablecodeaholicguy/ai-devkit/skills/dev-pr is public and reachablegithub.com/codeaholicguy/ai-devkit/tree/HEAD/skills/dev-pr ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/codeaholicguy/ai-devkit/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/codeaholicguy/ai-devkit/blob/HEAD/skills/dev-pr/S ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/codeaholicguy/ai-devkit/blob/HEAD/skills/dev-pr/S ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 47 linesgithub.com/codeaholicguy/ai-devkit/blob/HEAD/skills/dev-pr/S ↗Pass
SKILL.md
View on GitHubDev PR
Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.
Contract
- Verify repository context with
git status -sb,git branch --show-current, andgit remote -v. - Confirm the branch is not the base branch and has committed changes to publish.
- Fetch the remote before comparing or rebasing.
- Rebase the feature branch onto the latest remote base branch before push/review.
- Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.
- Push safely. Use
--force-with-leaseonly when a rebase rewrote an already-pushed branch. - Open or update the host's review request: PR, merge request, or equivalent.
- Report review URL, branch, HEAD SHA, validation results, push mode, and risks.
Publish Workflow
- Inspect local context:
git status -sbgit branch --show-currentgit remote -v
- If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.
- Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to
origin/mainonly when that matches the repo. - Fetch the remote, inspect the delta, and rebase onto the remote base branch.
- If conflicts occur, inspect conflicted files and
git diff, resolve minimally, validate when useful,git add, then continue the rebase. Stop if the correct resolution is unclear. - Run relevant validation for the changed surface.
- Push:
- First push: set upstream.
- Normal update: plain push.
- Rebased already-pushed branch:
--force-with-lease.
- Open or update the review request using the host's tool/API/UI (
gh,glab, forge CLI, web UI, or project-specific workflow). - Write a concise review description. Include enough for reviewers to understand:
- Summary: what changed, why, and how.
- Validation: how it was verified.
- Risks: notable risks or "none known".
- Report:
- Review URL and state
- Branch and HEAD SHA
- Validation commands and exit codes
- Push mode, including whether
--force-with-leasewas used - Risks, follow-ups, or blockers
Files in this skill
2dev-pr skill questions
How do I install the dev-pr skill in Claude Code?
Run npx degit codeaholicguy/ai-devkit/skills/dev-pr ~/.claude/skills/dev-pr. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the dev-pr skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What should the agent do if there are uncommitted changes?
The agent must stop and ask the user to run the commit workflow first, as it does not stage or commit changes.
How does the agent handle pushing a branch that has already been pushed and then rebased?
The agent uses the --force-with-lease flag to push safely when a rebase has rewritten an already-pushed branch.
What information is included in the final report?
The report includes the review URL, branch name, HEAD SHA, validation results, push mode, and any identified risks.