create-pr

Open a PR for a small fix in the jackin' repo — typo, dependency bump, one-line bugfix, doc tweak — that needs no roadmap item. Also the shared PR-mechanics path other skills reuse. Commits inline; no separate commit skill.

jackin' rule files auto-load —

PULL_REQUESTS.md

.github/

agent rules,

BRANCHING.md

COMMITS.md

. This skill sequences them, never restates them. Read them for full rules.

When to use

Operator runs
```
/jackin-dev:create-pr
```
.
Small, self-contained change (no design, no roadmap item).

When NOT to use

Feature/idea worth a roadmap item →
```
/jackin-dev:propose
```
.
Implementing a finalized roadmap item →
```
/goal Implement <slug>.md
```
.

Arguments

```
--branch <name>
```
— explicit branch name.
```
--auto-branch
```
— pick the branch name yourself, no confirmation.
```
--title <msg>
```
— commit + PR title (else derive from the diff, Conventional Commits).

Process

Branch. Never commit to
```
main
```
. If on
```
main
```
, create a
```
fix/
```
/
```
chore/
```
/
```
docs/
```
/
```
refactor/
```
-prefixed branch named from the change. Suggest and confirm unless
```
--auto-branch
```
or
```
--branch
```
given.
Commit. Uncommitted changes → commit inline per
```
COMMITS.md
```
: Conventional Commits subject, DCO sign-off (
```
git commit -s
```
). Already committed → skip. Then
```
git push
```
.
Build the body.
```
[bin]
```
Run
```
cargo xtask pr body --base origin/main > /tmp/pr-body.md
```
. The classified change digest (rust / docs / capsule / schema + file list) prints to stderr — read it; the body skeleton goes to the file: the PR template (read from
```
.github/PULL_REQUEST_TEMPLATE.md
```
at runtime) with the verify-locally blocks already selected and byte-exact, prose left as placeholders. Block selection: Checkout + isolation env always; Rust tests on a Rust change; Docs checks + walk on
```
docs/**
```
; jackin-capsule smoke (with
```
--capsule
```
before any
```
console
```
/
```
load
```
) on
```
crates/jackin-capsule/
```
; schema migration smoke on a versioned-schema touch.
Fill + create.
```
[agent]
```
Edit
```
/tmp/pr-body.md
```
— write the prose sections (Summary, What ships, Behavior changes) from the digest + diff; drop the optional sections you do not need. Then
```
gh pr create --body-file /tmp/pr-body.md
```
. The binary already wrote the body, so there is no heredoc to quote.
Verify render.
```
gh pr view <PR> --json body -q .body
```
— confirm the prose you added renders (no stray
```
\`` or 
```
$
```
from hand-editing). Fix with
```
gh pr edit --body-file` if needed.
Reply. Share the PR URL and repeat the Verify-locally commands in your final message.

Common mistakes

Committing to
```
main
```
instead of a branch.
Hand-building the body or template instead of
```
cargo xtask pr body
```
— it reads the template and selects the verify blocks for you.
Posting the skeleton with the prose placeholders left unfilled.
Deployed docs URLs in the body (break post-merge) — refer to docs by name.

Tooling

cargo xtask pr body

(jackin' repo) emits the change digest + the template skeleton with verify-locally blocks auto-selected from the diff. Shared with

propose

. The binary guarantees the mechanical parts (block selection, capsule ordering, exact command text, heredoc quoting); the agent writes the prose.

create-pr

NPX Install

Tags

SKILL.md Content

create-pr

When to use

When NOT to use

Arguments

Process

Common mistakes

Tooling