create-pull-request (cline)

Turns a finished feature branch into a review-ready GitHub pull request — confirming the branch and base, summarising the commits into a description, filling the repo's PR template, and opening it with the `gh` CLI. It is about PUBLISHING your own work for review, not judging someone else's PR, crafting the individual commits, or tagging the release that follows.

A situation it fits

I finished work on a local branch and want to put it somewhere teammates can read and comment; I need to write a concise summary, point it at the right target branch, and publish it on the project's hosting site.
create-pull-request (cline). create-pull-request (cline) takes a completed branch and prepares it for team review by assembling the summary, choosing the appropriate target branch, filling the repository template, and opening the change on the hosting service. The other skills handle commit wording, release cutting, or history surgery — none of which actually publish the branch for review.

5 scenarios in the bank answer to create-pull-request (cline). The rest are in the game.

Skills it gets confused with

These share a family with create-pull-request (cline), which is another way of saying they are the ones you might reach for by mistake.

Knowing what create-pull-request (cline) does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

create-pull-request (cline) is part of cline/cline. Licence: Apache-2.0. The description above was written for this game, not taken from the skill.

← All skills