Pr Description Writer

Writes clear pull request descriptions by analyzing your branch diff. Covers what changed, why, how, and what to test. Works with GitHub, GitLab, and Bitbucket.

Install
cmdop skills install agensi-pr-description-writer

PR Description Writer is a skill published by agensi that reads a branch diff against the base branch and produces a complete pull request description. Rather than filling in a generic template, it derives its output directly from the actual code changes in the diff, which means the description reflects what was genuinely modified rather than boilerplate. The generated description covers four areas: what changed in the code, why the change was made, how the implementation was approached, and what reviewers should test before approving. This makes it practical for both the author who wants to save time writing and for reviewers who need context before reading the diff. The skill supports the formatting conventions used by GitHub, GitLab, and Bitbucket, so the output can be pasted or submitted directly to any of those platforms without reformatting. There are no environment variables required and no package registry entry listed, meaning it operates as a standalone skill within a compatible agent runtime. It is suited to any workflow where pull requests are regularly submitted and descriptions are frequently left empty or underspecified.

Use cases

  • Generate a full PR description from a branch diff before opening a pull request on GitHub
  • Produce reviewer-ready test instructions derived from the actual code changes
  • Create GitLab merge request descriptions that explain implementation decisions
  • Populate Bitbucket pull request bodies without manually writing them from scratch
  • Ensure every PR in a team workflow has a consistent, diff-accurate description

When to use it

  • When submitting pull requests to GitHub, GitLab, or Bitbucket and descriptions are consistently empty or minimal
  • When reviewers lack context about why a change was made or what to test
  • When automating PR creation in a CI or agent-driven workflow that needs description generation

When not to use it

  • When the target platform is not GitHub, GitLab, or Bitbucket, as formatting support is limited to those three
  • When the workflow does not involve a branch diff, such as direct commits to a shared branch
  • When a highly customized PR template with project-specific fields must be filled in, as the skill produces its own structure rather than populating an arbitrary form