Submit a pull request

Skill yegor256/courier/skills/submit-a-pull-request

Use this skill when the user wants to submit the current local branch as a pull request to a GitHub repository.From its SKILL.md

Install

npx -y skills add yegor256/courier --skill submit-a-pull-request

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 452 tokens by cl100k_base, as published. Nobody here has run it

Target

Target GitHub repository user named, or origin otherwise. Use repository's actual default branch as base. Resolve base branch at runtime, never hard-coding main.

Preconditions

Refuse on default branch or with dirty working tree. Refuse when no commits sit ahead of default branch. Refuse when open pull request already targets same branch. Confirm branch is up to date with remote default.

Boundaries

Submit commits untouched. Skip editing, amending, rebasing, squashing, building, testing, and linting.

Branch

Push branch before opening pull request.

Title

Use imperative-mood title, not Fixes or Update. Derive title and body, never from branch name.

Body

Write body as few short paragraphs. Cover what changes, why, and any follow-up. Quote snippet of most important change, no longer than ten lines. Trust code to convey change better than prose.

Format

Shape pull request as imperative title plus short prose body. Shape comment as one or two sentences.

Voice

Write like human. Vary rhythm, never sliding into AI cadence. Open with substance, never with boilerplate or buzzword strings. End body on last sentence. Skip Generated with footers, Co-Authored-By trailers, and robot emoji.

Closing

Use closing keyword only when user or commit already cites issue.

Owner

Read owner from repository slug. For organization, use top recent committer as owner. Stop when owner stays unknown. Ask user to resolve it.

Comment

Skip comment when owner is authenticated account. Post one follow-up comment to owner otherwise. Mention owner in that comment. Offer to clarify in that comment. Keep comment to one or two sentences. Ping one account. Let owner set their own timing.

Example

Branch 42-retry adds retry logic and user says "open PR". Push branch to origin. Title pull request Add retry to courier client. Write few short paragraphs covering change and motivation. Quote most important change, under ten lines. Ping owner once in follow-up comment.

Stop

Stop after comment, or after pull request when you skip comment.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 452 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Derive title and body from content
Quote important changes under ten lines
Write like a human
Ping owner in follow-up comment
Ask user to resolve unknown owner

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.