Menú
Use when the user asks to create a pull request. Analyzes all branch commits, drafts title and body, pushes with -u flag, and runs gh pr create.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
System design and architecture decisions. Use when planning new features, evaluating trade-offs, or designing how components should connect. Proposes 2-3 approaches and recommends one.
Smart commit workflow. Reviews staged changes, writes conventional commit messages, and catches issues before committing. Use when ready to commit work.
Quality review of completed work. Use after making changes and before claiming completion. Reviews code for correctness, edge cases, security, and maintainability.
Systematic debugging workflow. Use when diagnosing bugs, test failures, or unexpected behavior. Follows a rigorous reproduce → isolate → hypothesize → fix → verify cycle.
Systematic multi-agent research. Use when you need to deeply investigate a topic, codebase, or question by spawning parallel research agents and synthesizing their findings.
Deep code explanation. Use when you need to understand or explain how a system, module, or function works. Traces data flow, maps dependencies, and explains design decisions.
| name | quick-pr |
| description | Use when the user asks to create a pull request. Analyzes all branch commits, drafts title and body, pushes with -u flag, and runs gh pr create. |
When the user asks to create a PR, follow this exact protocol.
git status # untracked files (never use -uall)
git diff && git diff --staged # uncommitted changes
git log --oneline main..HEAD # all commits on this branch
git diff main...HEAD # full diff from base branch
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null # check remote tracking
If there are uncommitted changes, ask the user if they want to commit them first before creating the PR.
Analyze ALL commits on the branch, not just the latest one.
## Summary
- [1-3 bullet points describing what changed and why]
## Test plan
- [ ] [How to verify the changes work]
# Push with tracking (create branch if needed)
git push -u origin <branch-name>
# Create PR using HEREDOC for body
gh pr create --title "the pr title" --body "$(cat <<'EOF'
## Summary
- bullet points here
## Test plan
- [ ] verification steps here
EOF
)"
-u flag to set upstream trackinggh pr create — not the GitHub web interface