Agent skill · writing content · aiskillstore
create-pr
Generate commit message, PR title, and PR body for a pull request. Use when the user wants to create a PR, generate PR content, prepare a pull request, or fill a PR template from code changes.
Why this skill is useful
Adds a detailed automated process for generating PR content, including commit messages and PR templates, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Create Pull Request Content Generate all content needed for a pull request: commit message, PR title, and PR body. Step 1: Gather Information YOU MUST EXECUTE THESE COMMANDS IN ORDER. DO NOT SKIP ANY STEP. Step 1.1: Get branch info: Step 1.2: Get file change summary (THIS IS CRITICAL - you must see ALL files): Step 1.3: Get the full diff (committed + staged changes): Step 1.4: Find the PR template: Step 1.5: Check for JIRA ticket: CRITICAL: The PR summary MUST mention ALL files shown in the Step 1.2 --stat output. Count the files and verify your summary accounts for all of them. Step 2: Generate Output Output ONLY the following format. Start immediately with "COMMIT MESSAGE:" - no preamble or commentary: IMPORTANT formatting rules: Section labels must be plain text exactly as shown: "COMMIT MESSAGE:", "PR TITLE:", "PR BODY:" Do NOT use markdown formatting on the labels (no bold, no code blocks around them) Separate sections with exactly "---" on its own line The PR BODY content can contain any valid markdown (code blocks, lists, etc.) Commit Message Guidelines One line only, maximum 80 characters Start with a verb (Add, Fix, Update, Remove, Refactor, etc.) Be specific but concise No period at the end NO footers, NO co-authors, NO signatures PR Title Guidelines One line only, maximum 80 characters Should summarize the overall purpose of the PR Can be similar to commit message but may be slightly more descriptive PR Body Guidelines Summary IMPORTANT: The Summary section heading must be ## Summary (h2), not # Summary (h1). Structure the summary as follows: 1. Start with a short paragraph describing the big picture of the changes 2. Follow with Key changes: (bold) 3. Add a bullet list of all changes made, one per line. Similar changes can be summarized together. Types of changes CRITICAL: Preserve ALL checkbox items from the template exactly as they appear. Mark applicable items with [x] and leave non-applicable items as [ ]. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/create-pr--13eced