Menú
{{ ƔƔƔ }} Create a pull request to main — wordy or shiny (with screenshots), ready-for-review or draft
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
{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).
{{ 𝛀𝛀𝛀 }} Create a project roadmap in the rich phase-array format — roadmaps.json as source of truth plus a PHASE task list and prose overview
{{ 𝛀𝛀𝛀 }} Recompute and synchronise roadmap task statuses across roadmaps.json and its projections, with optional codebase reconciliation
{{ 𝛀𝛀𝛀 }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity — ID assignment, status computation, dependency edges in both directions, and no unconnected islands.
Git workflow: branch management, commit conventions, PR patterns, conflict resolution.
{{ 𝛀𝛀𝛀 }} Review a pull request and post it as a GitHub review
| name | PR: Create |
| description | {{ ƔƔƔ }} Create a pull request to main — wordy or shiny (with screenshots), ready-for-review or draft |
| when_to_use | When a branch is ready (or nearly ready) to open as a PR and needs a description written from its commits. |
| model | sonnet |
| disable-model-invocation | true |
| allowed-tools | ["Bash(git:*)","Bash(gh:*)","Read","Glob","Grep"] |
| argument-hint | [shiny|wordy] [draft] [screenshot files or issue numbers...] |
mainReplaces the former pr-shiny-create / pr-shiny-draft / pr-wordy-create / pr-wordy-draft quartet: one skill, two axes.
<pull-request-create>
<arguments>
<axis name="style">First token of $ARGUMENTS if it is `shiny` or `wordy`. Default: `wordy`. Shiny adds a Screenshots section.</axis>
<axis name="mode">If the token `draft` appears anywhere in $ARGUMENTS, create the PR as a draft. Default: ready for review.</axis>
<axis name="extras">Remaining tokens: screenshot file paths (shiny) or issue numbers to close (wordy). Empty means no screenshots section content / no issue-closing line — never invent either.</axis>
</arguments>
<steps>
<step num="1">Look at the commits on this branch (`git log` against `origin/main`)</step>
<step num="2">Analyse the overall effect of these changes if merged into `main`</step>
<step num="3">Fill the template at `~/.claude/library/templates/pr-description.md` exactly — each {{ slot }} describes its content. For wordy style, omit the Screenshots block entirely (and its trailing `---`). For shiny style, one collapsible `<details>` per named screenshot.</step>
<step num="4">Show the draft description and **stop for approval**. If changes are requested, incorporate them and repeat step 3.</step>
<step num="5">On approval, create the PR to `main` with `gh pr create` — add `--draft` when mode is draft. Report the PR URL.</step>
</steps>
<rules>
<rule>The template is the single source of the body structure — do not restructure it.</rule>
<rule>Title: brief, descriptive, title case, understandable to non-devs.</rule>
<rule>Summary: a non-technical, absurd metaphor.</rule>
<rule>TL;DR: steps devs must take after pulling this down.</rule>
<rule>Changes: break into files or categories depending on PR scope; use collapsible details.</rule>
</rules>
</pull-request-create>