Open Pr
Push the current branch and open a pull request against the detected base branch, with an AI-drafted title and body confirmed by the user before creating. Use when the user wants to open, create, or submit a PR — phrases like "PR 올려줘", "PR 열어줘", "PR 만들어줘", "open a PR", "create a pull request", "submit for review", "/open-pr". Do NOT use to review, comment on, or update an existing PR.
Install
$ agentstack add skill-dkmqflx-git-workflow-plugin-open-pr ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dkmqflx-git-workflow-plugin-open-pr) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Open PR
Push the current branch and open a pull request via gh pr create.
Run this after committing your changes (see commit-each). Once the PR is merged, clean up with branch-done or worktree-done.
When to apply
Opening a new PR for the current branch. Do not apply to update, review, or comment on an existing PR.
Steps
- Determine the base branch:
- Try
git symbolic-ref refs/remotes/origin/HEADand strip therefs/remotes/origin/prefix. - If that fails, use the first of
dev,main,masterthat exists locally (git show-ref --verify --quiet refs/heads/). - If none exist, stop and ask the user which branch is the base.
- Record the current branch:
git rev-parse --abbrev-ref HEAD. If it equals the base branch, stop and notify the user — there's nothing to open a PR from. - Check for uncommitted changes (
git status --porcelain). If any exist, stop and tell the user to commit first. - Check whether a PR already exists for this branch:
gh pr view --json url 2>/dev/null. If one does, stop and report its URL instead of creating a duplicate. - Push the branch:
git push -u origin HEAD. - Gather context for the PR description:
``bash git log ..HEAD --oneline git diff ...HEAD ``
- Draft a title (under 70 characters) and a body with a
## Summary(1–3 bullets) and## Test plan(checklist) section, covering all commits on the branch — not just the latest. - Show the drafted title and body to the user and get confirmation before creating.
- Create the PR:
``bash gh pr create --base --title "" --body "$(cat EOF )" ``
- Report the returned PR URL.
Guardrails
- Always confirm the drafted title/body with the user before running
gh pr create— opening a PR is visible to others and not easily undone. - If
ghis not installed or not authenticated, stop and tell the user to rungh auth login. - Never force-push (
git push -f) to publish the branch. - Do not create a second PR if one already exists for this branch.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dkmqflx
- Source: dkmqflx/git-workflow-plugin
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.