tibursocampos/agent-dev-toolkit / core/skills/open-github-pr
open-github-pr
VerifiedCreate a GitHub pull request with gh CLI against the repository's base branch, template resolution, mandatory title/body confirmation, and mandatory auto-merge ask. Use whenever the user wants a PR opened — including /open-github-pr, open PR, create pull request, abrir PR, criar PR, abrir o PR, faça o PR, fazer o PR, open the PR, open a pull request, fluxo completo (when PR is in scope), commit+push+PR, push and open PR, release PR, or any handoff from /commit or /push that implies opening a pull request. Never create a PR with ad-hoc gh commands outside this skill; follow this SKILL.md end-to-end.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.0 KB |
| reference.md | markdown | 741 B |
| references/confirm-and-create.md | markdown | 2.1 KB |
| references/draft-title-body.md | markdown | 347 B |
| references/ensure-pushed.md | markdown | 408 B |
| references/guards-and-mode.md | markdown | 1.5 KB |
| references/must-not.md | markdown | 857 B |
| references/preflight.md | markdown | 1.3 KB |
| references/resolve-template.md | markdown | 510 B |
| references/validate-branch.md | markdown | 402 B |
| templates/feature-pr.md | markdown | 632 B |
references/confirm-and-create.md
View on GitHub## Confirm with user (mandatory)
Detect whether the repo allows auto-merge:
```bash
gh api repos/{owner}/{repo} --jq .allow_auto_merge
```
Present title, base, head, full body, template source path, and auto-merge availability. Ids and render rule: `core/skills/_shared/agents/QUESTIONS.md`. Ask two questions in the user's chat language:
1. Content gate: `confirm` (create the PR), `adjust` (the user says what to change), `cancel` (do not create it).
2. Auto-merge gate: `confirm` (enable auto-merge after create) or `decline` (do not enable). State whether the repository allows auto-merge, from the `allow_auto_merge` check above.
Only a `confirm` on the content gate creates the PR. Apply `adjust` changes and re-confirm. Silence, an ambiguous or unrelated reply, or a lone emoji is not approval; a clear affirmative reply in any language is.
**Auto-merge question is mandatory every time** — including when the user already said “fluxo completo”, “abra o PR”, or similar. Do not infer auto-merge from those phrases. Ask even when unavailable; if the answer is `confirm` but `allow_auto_merge` is false, create the PR and report that auto-merge cannot be enabled.
## Create PR (and optional auto-merge)
Write the approved body to a temp file, then:
```bash
gh pr create --base <base> --head <head> --title "<approved title>" --body-file <path-to-approved-body.md>
```
### Merge method (the repository decides)
This skill does not pick a merge method. Use the one the repository requires:
1. Its rulesets, if any: `gh api repos/{owner}/{repo}/rulesets`.
2. Its docs or PR template, if they state one.
3. If none of them states a method, ask the operator which one to use. Do not guess.
Auto-merge with the chosen method:
```bash
gh pr merge <number-or-url> --auto --<method> --subject "<approved PR title>"
```
If the repository disables the chosen method, **STOP**, report which method is blocked, and ask the operator. Do not silently fall back to another method.
Report the PR URL.
## Report
- Base and head
- PR URL and number
- Merge method used and auto-merge status (enabled / skipped / unavailable)
- Template source path used
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |