Menu
Create a PR to provided base branch using the pull request template. Use when opening a new PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Opinionated conventions for authoring, restructuring, and reviewing agent skills. Use when deciding whether guidance belongs in `SKILL.md`, a conditional reference, or a smaller skill; writing trigger descriptions and reference routers; naming procedural or documentary skills; creating examples; keeping skill context focused; or bundling static assets and their licenses.
Opinionated conventions for designing focused agent-skill plugins as encapsulated, installable capabilities. Use when defining a plugin boundary, deciding which skills are public entry points, hiding shared implementation skills, splitting broad plugins, designing plugin structure, minimizing client manifests, or removing auxiliary package documentation.
Opinionated language-agnostic design rules for implementation, refactoring, and code review. Use when shaping conditional control flow, finite states, invariants, error boundaries, resource lifetimes, abstractions, public APIs, validation boundaries, pagination, missing values, or the separation of sans-I/O decisions from imperative drivers.
Opinionated language-agnostic test-admission and sans-I/O unit-testing rules. Use when proposing, writing, reviewing, or deleting tests; deciding whether behavior is project-owned; evaluating wrapper, schema, ORM, framework, mock, or third-party-library tests; or separating pure business policy from wiring and I/O.
Opinionated feature-first architecture conventions for cohesive modules, owned subtrees, entry points, shared-code promotion, and package boundaries. Use when designing or reviewing directory structure, placing UI or workflow code, splitting nested capabilities, extracting shared modules, enforcing feature import boundaries, deciding whether a feature deserves a package, or refactoring horizontal technical layers.
Opinionated `better-all` conventions for dependency-declared async task graphs, inferred task results, cancellation propagation, and failure semantics. Use when replacing serial `await` chains or manual `Promise.all` stages, parallelizing work with result dependencies, or writing and reviewing `all` and `allSettled` task definitions.
| name | open-pr |
| description | Create a PR to provided base branch using the pull request template. Use when opening a new PR. |
| user-invocable | true |
| argument-hint | [base-branch] |
| arguments | ["base"] |
Summarize the latest changes in this branch to create a pull request on GitHub.
$base argument if provided, otherwise the repository's default branch (origin/HEAD):
git log "${base:-origin/HEAD}"..HEAD --oneline
git diff "${base:-origin/HEAD}"...HEAD
Make sure to only focus on the finalized implementation details. Since pull requests tend to have work-in-progress commits at the beginning, you should be extra mindful on whether these are still relevant in the finalized snapshot.
2. Use the pull request template to generate a .agents/scratchpad/PR.md.
3. Pause here and prompt the user to check the .agents/scratchpad/PR.md before proceeding.
4. Once edited and approved by the user, fill in the missing details in the following script and then run it. With no $base, gh targets the repository's default branch:
gh pr create ${base:+--base "$base"} \
--head "$(git rev-parse --abbrev-ref HEAD)" \
--title '[TICKET-123] category: short title' \
--body-file .agents/scratchpad/PR.md
.agents/scratchpad/PR.md once successfully submitted.