PR Creator: House-Style PRs Without the Hype

Where this fits

You've just finished a long coding session. Your agent has made 20 commits, some labeled "fixup", others "WIP". You ask: "Create a PR for this." What comes back is a wall of raw diff summaries—not something you'd post in Slack. pr-creator solves this by turning that chaotic commit history into a clean, house-style pull request: a title that matches your team's conventions, a body that links the right issues, and a draft state if you're not ready for review. It's the difference between an AI that dumps output and one that acts like a thoughtful teammate.

Why agents benefit

• House-style automatically: It learns your repo's PR templates and applies them, so every PR looks like it was written by a human who knows the project.
• Issue linking from context: It parses branch names, commit messages, and conversation to link the correct issues—no manual copy-paste.
• Commit hygiene: It can squash, reorder, or split commits to make the diff readable, reducing reviewer cognitive load.
• Draft state control: It sets the PR as draft when you're still iterating or marks it ready when you explicitly ask.
• Skill delegation: It knows when to hand off to tidy for code fixes, pr-babysitter for CI and review threads, or autoship for releases—so you don't get a one-size-fits-all mess.

Practical scenarios

From messy commits to a clean PR

Your agent has been working on a feature branch with 15 commits, including three "address review" commits. You say "polish the PR". pr-creator restructures the commits, squashes the noise, and writes a body that explains the what and why—not just a list of files changed.

Rewriting a PR description after review

A reviewer says the PR description doesn't match the final implementation. Instead of manually editing, you tell the agent "rewrite the PR description". pr-creator updates the body to reflect the current diff, re-links issues, and adjusts the title to match the actual scope.

Creating a draft PR for early feedback

You want early feedback on a large change, but it's not ready. You ask for a draft PR. pr-creator creates the PR in draft state, includes a clear checklist of remaining work, and links the relevant issue—so your team can comment without thinking it's merge-ready.

Add it to your agent workflow

Install the skill with:

npx skills add mblode/agent-skills --skill pr-creator

Then simply ask your agent: "Create a PR for the branch feature/user-auth, link issue #42, and set it as draft." The agent will use pr-creator to handle the rest—titles, templates, and commit cleanup.

Compare before adopting

Before you commit, compare pr-creator against alternatives based on:

• Quality signals: Does it produce PRs that read like a senior dev wrote them? Check the README's examples and the references/pr-polish.md workflow.
• Maintenance freshness: Is the repo actively maintained? Look at recent commits and issue responses.
• Alternatives: Other skills or manual PR writing—what's the overhead? pr-creator's clear boundaries (it doesn't touch code) make it a good fit for agent pipelines.
• Workflow fit: Does it integrate with your existing GitHub CLI setup? The documented workflow assumes authenticated GitHub access.

Why it is worth tracking

pr-creator has 104 stars and a focused, well-documented scope. The author, mblode, maintains a suite of agent skills, and this one fills a real gap—agents that create PRs are common, but few handle house style and commit hygiene properly. If your agents frequently open or update PRs, this skill is worth evaluating. Track its evolution and community feedback to see if it keeps pace with GitHub's changing API. For a deeper look, visit the skill page at https://www.openagentskill.com/skills/mblode-pr-creator.