create-pr

Create or update GitHub pull requests from internal story files.

1|Updated Jan 15, 2026

Search Tags:#automation #github #bash #CLI #pull-request #pr-management #story-driven

Ready to run

npx skills add https://github.com/qmu/workaholic --skill create-pr-qmu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/create-pr
Command: npx skills add https://github.com/qmu/workaholic --skill create-pr-qmu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

This Skill automates the creation and updating of GitHub pull requests directly from your internal story files, ensuring PRs reflect the latest work without manual copy-paste.

Core Features & Use Cases

Derives PR titles from the first Summary item in the story file for consistent naming.
Creates new PRs or updates existing ones based on the branch, keeping PR content in sync with stories.
Generates PR bodies by stripping YAML frontmatter and including the story content, providing clear context for reviewers.
Use case: you write a new feature in .workaholic/stories/feature-branch.md; running the Skill creates or updates a PR on branch feature-branch with an appropriate title and content.

Quick Start

bash .claude/skills/create-pr/sh/create-or-update.sh <branch-name> "<title>"

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate GitHub pull request creation from markdown story files?▼

Automate GitHub pull request creation by running a CLI script that parses markdown story files to derive PR titles and bodies. This syncs PR content with planned changes without manual copy-paste.

How does a story-driven workflow generate PR titles from summary items?▼

Story-driven workflows generate PR titles by extracting the first Summary item from your story file. The script uses this item as the PR title to ensure consistent naming across feature branches.

Do I need gh and jq installed to automate pull request management from the CLI?▼

Yes, you need both gh and jq installed to automate pull request management. The script uses jq to strip YAML frontmatter from story files and gh to create or update pull requests on GitHub.

Can I update an existing GitHub PR with new content from a story file?▼

Yes, you can update an existing GitHub PR by running the script against your current branch. It checks for an existing PR and updates its body with the latest story content, removing the YAML frontmatter.

What is the best way to keep GitHub PR bodies in sync with internal planning documents?▼

The best way to keep PR bodies in sync is to generate them directly from internal story files. This ensures the PR body reflects the latest planned changes by removing frontmatter and including the story content.