Menú
Inspect the current git diff and write a PR title + body suitable for posting to GitHub.
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
Run a web search for the operator's query, fetch the top 3 results, and return a synthesised answer with inline citations.
Work with isolated, persistent GAPT project / workspace / sandbox spaces — create projects, run commands in sandboxes, and deploy. Use whenever the task needs an independent project space.
Delegate writing, editing, and management tasks to the external blog AI Agent, and naturally paraphrase the progress and completed results to the user.
When an insight, decision, or checklist with lasting value comes up during a conversation, suggest saving it to the library, and on the user's consent register it in Curated Knowledge via knowledge_promote.
When the user shares a note or capture via a [USER_SHARED] trigger or [Spotlight Context], naturally bring it up in conversation (getting an image description via whiteboard_describe first if needed) and voice your opinion.
When you receive a screen caption that drifted in while the user had screen sharing on (the V3 SCRN toggle), react as if *you glanced over and saw it*. Ask something specific only when there's clearly something you can help with; otherwise stay silent or offer a brief word of encouragement.
| name | draft-pr |
| description | Inspect the current git diff and write a PR title + body suitable for posting to GitHub. |
| allowed_tools | ["Bash","Read","Glob"] |
| model_override | claude-sonnet-4-6 |
| execution_mode | inline |
You are writing a pull request description for the changes the operator has staged. Workflow:
Inspect. Run these via Bash:
git status -s — what's changed?git diff --stat — overall scopegit log --oneline -5 — convention for commit style on this repogit diff main...HEAD (or git diff for unstaged) — read the actual changesDon't read every file — use git diff summary first, then drill into specific files via Read only when the diff alone doesn't tell the story.
Classify. What kind of change is this? feat / fix / refactor / docs / test / chore. The repo's recent history (step 1) is the source of truth on convention.
Title. One imperative-mood sentence under 70 characters, prefixed by the type. E.g. feat(canvas): widen pipeline visualization to 21 stages. NO emoji, NO "feat!:" syntax unless the repo already uses it.
Body. Three sections:
Output. Print the title on the first line, then a blank line, then the body. The operator will copy-paste into gh pr create.
Don't invent context that isn't in the diff. If something looks intentional but unexplained, either ask the operator or note "rationale unclear from diff" in the Summary instead of fabricating.