Skip to content
Skills Library
Programming · Tool integration

write-pr-description

/write-pr-description

Write a pull request title and description from the actual changes on a branch, then open the pull request or update an existing one on Bitbucket or GitHub using the OmniDev tools. Use when the user asks to raise a PR, write or refresh a PR description, or says a branch is ready for review.

Repository
OmniDev ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 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.
Content25 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

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

What it does and when to use it

Write a pull request title and description from the actual changes on a branch, then open the pull request or update an existing one on Bitbucket or GitHub using the OmniDev tools. Use when the user asks to raise a PR, write or refresh a PR description, or says a branch is ready for review.

Original author description

Write a pull request title and description from the actual changes on a branch, then open the pull request or update an existing one on Bitbucket or GitHub using the OmniDev tools. Use when the user asks to raise a PR, write or refresh a PR description, or says a branch is ready for review.

How it works

  1. 1. Find out what changed
  2. 2. Draft
  3. 3. Show the user
  4. 4. Open or update
  5. Never
Original SKILL.md headings · 54 lines, 349 words
SKILL.md preview
---
name: write-pr-description
description: Write a pull request title and description from the actual changes on a branch, then open the pull request or update an existing one on Bitbucket or GitHub using the OmniDev tools. Use when the user asks to raise a PR, write or refresh a PR description, or says a branch is ready for review.
---

# Write a pull request description

A reviewer reads the description before the code. It should tell them what
changed, why, and how to check it, without making them read the commit list.

## 1. Find out what changed

In the user's working copy:

1. Find the source branch (the current branch) and the target branch. If the
   target is not obvious, ask.
2. Read `git log <target>..HEAD` and `git diff <target>...HEAD`.
3. Look for a pull request template in the repository, such as
   `.github/pull_request_template.md`. If there is one, use its headings.

## 2. Draft

Without a template, use these headings:

- **What:** the change in one or two sentences, in terms of behaviour.
- **Why:** the problem it solves and why this approach was chosen.
- **How to verify:** commands to run or steps to follow, and what to expect.
- **Notes for the reviewer:** risks, follow-ups and anything left out on
  purpose. Leave the heading out if there is nothing to say.

Rules for the text:

- Describe the change as it is now, not the story of how it was written.
- Say a test or a build passes only if you ran it in this conversation.
- Keep it short. Link to an issue; do not paste it.
- For the title, follow the convention the repository's recent commits use.

## 3. Show the user

Show the title and the description exactly as they will be posted and ask for
approval or edits.

## 4. Open or update

- **A pull request already exists:** call `pr_update` with its URL, the new
  title or description, and `confirmed: true`.
- **No pull request yet:** check that the branch is pushed. If it is not, ask
  before pushing. Then call `pr_create` with the repository URL from
  `git remote get-url origin` (converted to its https web address), both
  branches, the title, the description and `confirmed: true`.

Give the user the pull request URL from the result.

## Never

- Open, update or push without the user's approval in this conversation.
- Describe changes that are not in the diff.

Versions

RepositoryScoreLicence
This page · kashishparmar02/OmniDev90MIT
Agenta-AI/agenta100MIT
warpdotdev/common-skills100MIT
shivaedev/pardes100MIT

Database snapshot: 13.11.2026 · package version 9604506b0312 (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
    Use when writing or updating a pull request or merge request description for the current branch, for GitHub, GitLab, or Bitbucket.
  • 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".
  • 100v1-pr-description
    Use when writing or updating a GitHub PR title or description. Triggers on "write PR description", "update PR body", or "PR title".
  • 100pr
    Write or update a pull request title and description from the actual changes and available evidence. Use when the user asks to prepare, open, describe or update a PR, or improve an existing PR description.
  • 90review-pr
    Review a Bitbucket or GitHub pull request using the OmniDev tools, then publish only the findings the user approves as inline comments. Use when the user shares a pull request URL and asks for a review, a second opinion, or "what's wrong with this PR".
  • 100writing-pull-requests
    Use when writing or rewriting a pull request description, PR title, or MR description. Triggers on "write the PR", "PR description", "raise a PR", "open a PR", "describe this branch", "summarise this change for review", "what should the PR say", and on being asked to improve a…

Feedback and reports

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