pull-request

name	pull-request
description	Create well-structured GitHub PRs enforcing issue-first discipline. Single source of truth — no /commands wrapper.
version	3.0.0
preconditions	["linked_issue_exists","issue_has_status_approved","tests_passing","branch_pushed_to_remote"]
outputs	[{"name":"pr_url","type":"url","format":"https://github.com/{owner}/{repo}/pull/{N}"},{"name":"pr_checklist","type":"checklist","format":"issue_linked | tests_pass | no_secrets | title_under_70_chars"}]
steps_count	5
when	{"keywords":["pull request","pr","open pr","create pr","github pr","submit for review"]}

pull-request

Create well-structured GitHub PRs. Issue-first enforcement: no PR without an approved issue.

When to invoke

• After finishing-a-development-branch selects "Push + PR"
• When user asks to "create PR", "open pull request", "submit for review"

Step 0 — Issue-first gate

Every PR MUST link an approved issue.

gh issue view <N> --json title,labels -q '{title: .title, labels: [.labels[].name]}'

STOP if any fail:

• Issue exists and is not closed
• Issue has status:approved label (maintainer-only — wait if missing)
• Issue number known — will add Closes #<N> in PR body

If no issue exists, run Skill('issue-creation') first.

Step 1 — Survey branch

git status
git log main..HEAD --oneline
git diff main...HEAD --stat

Step 2 — Verify tests pass

npm test  # or pytest / go test / cargo test
# Must see 0 failures before creating PR

Step 3 — Push branch

git push -u origin $(git branch --show-current)

Step 4 — Create PR

Title format:

tipo — Descripción imperativa en inglés (max 70 chars)

Examples:

feat — Add user authentication with JWT refresh rotation
fix — Resolve null pointer in UserService.findById
refactor — Extract payment service to shared module

gh pr create --title "tipo — Descripción imperativa" --body "$(cat <<'EOF'
## Linked Issue

Closes #<N>

## Summary

- [Bullet 1: qué se implementó y por qué]
- [Bullet 2: decisión clave tomada]
- [Bullet 3: qué se cambió / eliminó]

## Motivation

[Por qué se necesitaba este cambio — link a issue/ticket si aplica]

## Test Plan

- [ ] [Escenario de prueba 1]
- [ ] [Escenario de prueba 2]
- [ ] [Edge case probado]
- [ ] Tests existentes pasan (`npm test`)

## Breaking Changes

[Ninguno / Describir si los hay]

## Rollback Plan

[Cómo revertir si esto rompe producción — e.g. `git revert <sha>`, feature flag off]
EOF
)"

Step 5 — Confirm

gh pr view  # Show PR URL and status

Output the PR URL to the user.

Checklist before creating

• Linked issue with status:approved
• PR body contains Closes #<N>
• Branch pushed to remote
• Tests passing
• Title ≤ 70 chars, conventional format
• Summary bullets concrete (not "changed some files")
• Test plan concrete (not "tested manually")
• No secrets/credentials in diff

Hard rules

• NEVER Co-Authored-By footer
• NEVER tool attribution lines (Generated with…, 🤖 …)
• NEVER ticket IDs/tool names/branding in title
• NEVER force push to main/develop