Create PR with labels and assignment

VerifiedCaution

Push branch and open a Pull Request assigned to @me, labeled, with Closes #N link, following conventional commit style.

Sby Skills Guide Bot
DevelopmentIntermediate
7/26/2026
Claude Code
#git#pull-request#github-cli#changelog#conventional-commits

Recommended for

Automated summary

Automates opening a GitHub pull request from the current branch: updates the changelog, pushes, then creates a titled, labeled, self-assigned PR with a short body.

Strengths

  • Enforces a consistent PR shape: conventional title under 70 characters, a single label, body under 15 lines
  • Derives type and label from the branch prefix and pulls the issue title with gh issue view
  • Updates the [Unreleased] section of CHANGELOG.md and commits it before pushing
  • Reports the PR URL at the end

Limitations

  • Assumes a GitHub remote with an authenticated gh CLI, main as base branch, and a test plan mentioning composer test
  • Label vocabulary and branch-prefix mapping are hardcoded and must be edited for other conventions
  • Stops at the URL: it does not wait for CI or handle review or stacked PRs
When to use it

When a branch is ready and you want a consistent, assigned, labeled PR opened in one step.

When not to use it

On a non-GitHub remote, for stacked PRs, or when branch and label conventions differ from the hardcoded mapping.

Security analysis

Caution
Quality score88/100

The skill automates a standard developer workflow using git and gh. It does not contain destructive or exfiltrating instructions, but it does push code to a remote and create PRs, so it warrants a caution rating due to network and repository-mutating actions.

Findings
  • •Uses Bash with git and gh to push branches and create pull requests on a remote repository.
  • •Executes a shell heredoc within a command substitution to construct the PR body, which could be manipulated if branch names or issue titles contain unexpected characters, though the risk is low.
How this analysis is made

Examples

Open PR linked to an issue
/pr 142
Open PR with no linked issue
/pr

description: Push branch and open a PR (assigned to @me, labeled, Closes #N) argument-hint: "[issue-number]" disable-model-invocation: true allowed-tools: "Read, Edit, Bash(git *), Bash(gh *)"

PR

Context

!git branch --show-current !git log main..HEAD --oneline

Instructions

  1. If ## [Unreleased] in CHANGELOG.md wasn't updated, update it and commit: docs: update changelog.
  2. git push -u origin HEAD.
  3. Title: <type>(<scope>): <short> (conventional, under 70 chars). Derive type from branch prefix (feat/ → feat, fix/ → fix, docs/ → docs, ref/ → ref). If $ARGUMENTS is an issue number, pull the title via gh issue view <num> --json title -q '.title'.
  4. Pick one label: bug (fix/), enhancement (feat/), documentation (docs/), refactoring, pure testing, dependencies.
  5. Open:
    gh pr create --title "<title>" --assignee @me --label "<label>" --body "$(cat <<'EOF'
    ## Summary
    - <what + why, one or two bullets>
    
    ## Test plan
    - [ ] `composer test` green locally
    - [ ] CI green
    
    Closes #<issue-number>
    EOF
    )"
    
    Drop the Closes line if there's no linked issue. Body under 15 lines.
  6. Report URL.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-pr-with-labels-and-assignment-ms1aw3ep/download' --output '.skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep/SKILL.md.part' && mv '.skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep/SKILL.md.part' '.skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Edit, Bash(git *), Bash(gh *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-pr-with-labels-and-assignment-ms1aw3ep/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills