create-pr

Creates pull requests by orchestrating change summaries, title rendering, labels, and platform delegation.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill create-pr-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/create-pr
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill create-pr-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating pull requests requires assembling a change summary, formatting a conventional title, resolving labels, and calling the right platform API. This Skill automates that entire flow so a PR is created consistently from the current branch's change record. ## Core Features & Use Cases - Orchestrated PR creation: Derives session context, verifies branch sync with remote, summarizes the change, and resolves the effective scope, type, and breaking marker before creating the PR. - Title rendering and label resolution: Renders the PR title from a configurable template and maps type, scope, and breaking status to labels via a label-map file. - Platform delegation: Detects GitHub or Bitbucket from session context and delegates the actual API call to the matching internal skill, then persists the PR URL for later sessions. - Use Case: After finishing a feature branch, ask the agent to open a PR; it summarizes the change, renders a conventional title like "feat(api): add retry logic", applies labels, inserts the ticket closing line, and creates the PR on GitHub. ## Quick Start Create a pull request for my current branch using the create-pr skill.

Frequently Asked Questions about create-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a pull request automatically from a git branch?

Invoke the create-pr skill on your current branch. It derives session context, summarizes the change, renders a conventional title, resolves labels, and delegates the API call to GitHub or Bitbucket based on your repository configuration.

How are pull request titles and labels generated?

Titles are rendered from a configurable pr.title_format template using the effective record's scope, type, breaking flag, and ticket reference. Labels come from a .meta/label-map.json file mapping types and scopes, plus a breaking label when applicable.

Does this work with both GitHub and Bitbucket?

Yes. The skill reads the scm field from the session context manifest and delegates to create-gh-pr for GitHub or create-bitbucket-pr for Bitbucket. If the platform is unknown, it asks the user which one to use.

What happens if my branch is not up to date with remote?

The skill fetches origin and checks git status before proceeding. If the branch is out of sync, it stops immediately, emits a completion event with the stopped outcome, and notifies you rather than creating a stale PR.

Can I override the scope or type of the change summary?

Yes. Pass --scope or --type as optional arguments; they are forwarded to summarize-change and recorded as overrides. A trailing exclamation mark on the type, such as feat!, also marks the change as breaking.