Menü
Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when drafting, writing, or filing a Linear ticket/issue, or asked for a Linear title/body/description.
Writing voice for authored prose — PR bodies, Linear tickets, review comments, commit messages.
Hand a file to the user's running editor and block until they finish editing it. Use whenever a draft (PR body, ticket, commit message, any generated file) needs the user's review before you act on it, or when a task says "open this in my editor/vim/nvim".
Clojure style guidelines. Activate before writing or editing Clojure code
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
| name | pr-description |
| description | Use when drafting, writing, or opening a pull request (gh pr create), or asked for a PR title/body/description. |
Use the prose-voice skill.
## Test plan heading and no - [ ] checklists.## Summary / ## Why prose,
optionally a results table. Headings are fine at size.Direct gh pr create is blocked by a hook — this flow is the only path.
/tmp/pr-<slug>.md) using the template below.remote-edit skill (blocking open).PR_SKILL=1 gh pr create --title <title> --body-file <body> [flags].
The PR_SKILL=1 prefix is what the hook allows through — omit it elsewhere.---
# gh pr create fields — leave blank to omit. Title = first line below, body = rest.
base: # -B branch to merge into (default: repo default)
head: # -H branch with the commits (default: current)
reviewer: # -r handle(s), comma-separated
assignee: # -a login(s), @me for self
label: # -l name(s), comma-separated
milestone: # -m name
project: # -p title
draft: false # -d true to open as draft
no-maintainer-edit: false # --no-maintainer-edit
---
Title goes on this line
Body prose goes here.
Map each non-empty front-matter key to its flag (comma-separated values →
repeated flags, e.g. label: a,b → -l a -l b). Booleans emit the bare flag
only when true. Title comes from --title (first content line), body from
--body-file (the content after the title, written to its own temp file).