prkit

Draft and open GitHub pull requests from branch commits and diffs using the gh CLI.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill prkit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prkit
Source: https://github.com/mimukit/skills/tree/main/skills/prkit
Command: npx skills add https://github.com/mimukit/skills --skill prkit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a good pull request means re-reading your own branch, summarizing commits, filling in the PR template, and remembering to push, sync, and update the linked issue. This Skill automates that entire flow so the PR title, body, and test plan come from the actual commits and diff rather than from memory. ## Core Features & Use Cases - PR drafting from real changes: Generates a Conventional Commits-style title, summary, changes list, and test plan from the branch's commits and diff, filling in the repo's pull request template when one exists. - Full lifecycle handling: Syncs the branch with the base via rebase, pushes with force-with-lease when needed, creates or updates the PR with gh pr create/gh pr edit, and supports stacked PRs with correct per-layer bases. - Workflow integration: Embeds verifykit proof artifacts, flips the linked issue's label from in-progress to in-review, and moves dependent issues from blocked to stacked. - Use Case: After finishing a feature branch, ask the agent to open a PR; it fetches the base, writes the title and body from your commits, pushes the branch, creates the PR with the gh CLI, and hands off the PR URL. ## Quick Start Ask the agent to open a pull request for the current branch and it will draft the title and body from your commits, push the branch, and create the PR with the gh CLI.

Frequently Asked Questions about prkit

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the gh CLI: push your branch with git push -u origin HEAD, then run gh pr create --base <base> --title "..." --body-file <file>. This Skill automates that flow, generating the title and body from your branch's commits and diff.

How to write a good PR description from commits?

Derive the summary and test plan from the commit messages and diffstat rather than re-reading the entire diff. This Skill reads git log and git diff --stat against the base branch, fills the repo's pull request template if one exists, and references linked issues.

Does gh pr create work with stacked pull requests?

Yes, but each layer's base must be the branch below it, not the repo default. This Skill resolves the parent branch via gitkit and uses gh stack submit to open a PR per layer with correct bases in one command.

Why does my PR show merge conflicts right after opening?

The branch was behind the base branch when the PR was opened. This Skill checks with git rev-list --left-right --count and rebases onto the fetched base tip before pushing, so the PR opens with a clean, mergeable diff.

Can I draft a PR body without opening the pull request?

Yes. The Skill runs every step except the final gh pr create and prints the finished title and body instead. This also applies in environments without shell or gh access, where it outputs copy-pasteable markdown for the GitHub web form.