Skip to content
Skills Library
Programming · Writing

write-pr

/write-pr

Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description. Read-only — never opens or pushes the PR.

Licence
MIT
Last repository change
04.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
4
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (4). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description. Read-only — never opens or pushes the PR.

Triggers from the description

s diff and commit history, following the project

Arguments

/write-pr [base-branch]
Original author description

Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description. Read-only — never opens or pushes the PR.

How it works

  1. Use this skill when
  2. Do not use this skill when
  3. Context
  4. Instructions
  5. Output Format
Original SKILL.md headings · 137 lines, 766 words
SKILL.md preview
---
name: write-pr
version: 0.0.4
category: productivity
description: "Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description. Read-only — never opens or pushes the PR."
argument-hint: "[base-branch]"
---

# Write PR

Turn the current branch's changes into a PR title and body that match the project's existing conventions. Analyze git history and diffs for intent, not just file names.

## Use this skill when
- Writing or drafting a pull request description for the current branch
- Generating a PR title that matches the project's commit/PR style
- Filling in a PR template based on actual code changes

## Do not use this skill when
- The request is to actually open or push a pull request
- There are no commits ahead of the base branch
- The user only wants a commit message, not a PR description

**This skill is read-only. Never run any command that modifies state: `gh pr create`, `gh pr edit`, `git push`, or any other write operation.**

## Context

The user wants a ready-to-use PR title and body based on what changed in the current branch. Focus on **intent and impact**, not raw diff output. Respect the project's existing PR style.

## Instructions

### Step 1: Detect Base Branch

If `$ARGUMENTS` is provided, use it as the base branch.

Otherwise, auto-detect in this order:
1. Run `git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null` — extract branch name (e.g., `origin/main` → `main`)
2. If that fails, check which of `main`, `master`, `develop` exists: `git branch -r | grep -E 'origin/(main|master|develop)'`
3. Use the first match found

### Step 2: Collect Change Information

Run these commands in order:

```bash
git log <base>..<HEAD> --oneline
git diff <base>...<HEAD> --stat
git diff <base>...<HEAD> --shortstat
```

Use `--shortstat` output (e.g., `12 files changed, 340 insertions(+), 50 deletions(-)`) to determine diff size:
- **If changed files ≤ 20 AND insertions+deletions ≤ 500**: read the full diff with `git diff <base>...<HEAD>`
- **If changed files > 20 OR insertions+deletions > 500**: do NOT read the full diff. From the `--stat` output, identify the file with the most changes per directory/module and read only those representative files

### Step 3: Find PR Template

**This step is mandatory. Do not skip or assume the file does not exist.**

Attempt to read all paths below in parallel using a file read tool:
- `.github/PULL_REQUEST_TEMPLATE.md`
- `.github/pull_request_template.md`
- `docs/pull_request_template.md`
- `PULL_REQUEST_TEMPLATE.md`

Also check if `.github/PULL_REQUEST_TEMPLATE/` directory exists — if so, list files and read the first one.

Use the first path that successfully returns content.

**If a template file is successfully read:**
- Use its structure **exactly as-is** for the PR body
- Preserve all sections, headings, and HTML comments (`<!-- ... -->`) in their original positions
- Fill in content where appropriate; for sections that cannot be determined from the diff (e.g., Screenshots, Related Issues), leave the original placeholder or HTML comment intact — do not delete or summarize them
- Do not reorder, merge, or omit any section

**If all paths fail (file not found):** use this default structure:

```markdown
## Summary
<!-- What does this PR do and why? -->

## Changes
<!-- Key changes made -->

## Test Plan
<!-- How was this tested? -->
```

### Step 4: Identify PR Title Style

Run:
```bash
gh pr list --state merged --limit 10 --json title 2>/dev/null
```

If `gh` returns results, analyze the title patterns (e.g., `feat: ...`, `[PROJ-123] ...`, `Fix: ...`).

If `gh` fails for any reason (not installed, auth error, not a GitHub repo), fall back to:
```bash
git log --oneline -20
```

Extract the dominant pattern from commit messages.

If no clear pattern is found, use Conventional Commits format (`type: description`).

### Step 5: Write PR Content

**Title:**
- If the style detected in Step 4 is clear and consistent: produce **1 title**
- If the style is ambiguous or mixed: produce **2–3 title candidates**, clearly labeled

**PR Body:**
- Use the template structure from Step 3
- Fill each section based on the change analysis from Step 2
- Focus on **why** the change was made, not just what files changed
- Flag these explicitly if present in the diff:
  - Breaking changes (API/interface changes, removed fields)
  - New dependencies added
  - Architecture or structural changes
- Do **not** paste raw diff or file lists into the body
- For sections that cannot be filled (e.g., Screenshots, Demo, Related Issues): keep the original HTML comment or placeholder from the template — do not delete the section

## Output Format

Present the output in this order:

**Title**
```
<single best title>
```

*(If ambiguous, list alternatives labeled Alt 1, Alt 2)*

---

**PR Body**

```markdown
<filled-in PR body — exact template structure preserved>
```

---

> Branch: `<base>` ← `<current>` · Commits: N · Files changed: N
Files in this package (3)
  • README.ko.md 2 KB
  • README.md 2 KB
  • SKILL.md 5 KB

Versions

RepositoryScoreLicence
This page · 2ykwang/agent-skills100MIT
lvlup-sw/exarchos100Apache-2.0
daniel-kindl/dkstack100MIT
moonshotai/kimi-code96MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version cd01087c0378 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pr-description
    Write a pull request title and description for the current branch, and open the PR if asked. Use when the user says "open a PR", "create a pull request", "write the PR description", "describe my changes for review".
  • 100pr-describe
    Write a pull request title and description from the actual diff and commits, including a risk line and how to test. Use when the user asks to write, draft, fill in or improve a PR description, open a PR, or summarise a branch for reviewers.
  • 90pr-description
    Drafts pull request title and body from validated diff and opens or updates PR via GitHub MCP. Triggers when a change is ready to open or update a PR.
  • 100comms-pr
    Use when drafting or updating a Flowstate pull request title and body; the body follows the template's six sections and the commit-conventions check reads it.
  • 90gitflow
    Branches, commits, pushes and pull requests for this repo - naming, history rules, the PR title and a body filled from the PR template and the spec. Use when you create a branch, commit, push, or open or update a PR. Don't use for review comments on an open PR (use pr-comments-fix).
  • 100suggest-pr
    Suggest a pull request title and description for the current branch. Use when the user wants to open a PR, wants a PR description, or asks what to write for a pull request.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.