dev-pr
/dev-pr
AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.
- Author
- codeaholicguy ↗
- Repository
- ai-devkit ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.
Original author description
AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.
How it works
- Contract
- Publish Workflow
SKILL.md preview
--- name: dev-pr description: AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host. --- # Dev 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 1. Verify repository context with `git status -sb`, `git branch --show-current`, and `git remote -v`. 2. Confirm the branch is not the base branch and has committed changes to publish. 3. Fetch the remote before comparing or rebasing. 4. Rebase the feature branch onto the latest remote base branch before push/review. 5. Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation. 6. Push safely. Use `--force-with-lease` only when a rebase rewrote an already-pushed branch. 7. Open or update the host's review request: PR, merge request, or equivalent. 8. Report review URL, branch, HEAD SHA, validation results, push mode, and risks. ## Publish Workflow 1. Inspect local context: - `git status -sb` - `git branch --show-current` - `git remote -v` 2. If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill. 3. Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to `origin/main` only when that matches the repo. 4. Fetch the remote, inspect the delta, and rebase onto the remote base branch. 5. 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. 6. Run relevant validation for the changed surface. 7. Push: - First push: set upstream. - Normal update: plain push. - Rebased already-pushed branch: `--force-with-lease`. 8. Open or update the review request using the host's tool/API/UI (`gh`, `glab`, forge CLI, web UI, or project-specific workflow). 9. 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". 10. Report: - Review URL and state - Branch and HEAD SHA - Validation commands and exit codes - Push mode, including whether `--force-with-lease` was used - Risks, follow-ups, or blockers
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · codeaholicguy/ai-devkit | 90 | Apache-2.0 |
| pdl-openair/OpenAIR | 100 | Apache-2.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 260f95a86f1d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pr
Use when the user runs /pr to commit the current work, push the branch, and open or update its pull request. - 100create-pr
Open or update a GitHub pull request for the current branch — use when asked to create a PR, open a pull request, push and PR, or submit a PR. - 85code-pull-request
Manage GitHub pull requests or GitLab merge requests: create, read/leave/respond to comments, and merge. Triggers on "open a PR", "make a PR", "merge this PR", "merge the MR", "read PR comments", "leave a comment on the PR", "respond to a comment", "ship this", or when a feature… - 90gitlab-mr
Open a GitLab merge request for the current branch into the base branch — ready, not a draft, nobody assigned — through git push options, so only a read-only token is needed. If an MR is already open for the branch it only returns the link. Also fetches a bot's AI review of the… - 100pr-description
Use when writing or updating a pull request or merge request description for the current branch, for GitHub, GitLab, or Bitbucket. - 100bmad-github-story-open-pr
Push a story branch and open (or update) its GitHub PR: Closes the story issue, shares labels between the PR and the issue, and moves the issue to status:review. Use when Story Build or Story Dev invokes it, or when the user asks to open the PR for the current story worktree.