Skip to content
Get packs

Guide · Agent skill

How to use the GitHub PR Description Writer agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The github-pr-description skill is a set of instructions that tells an AI coding agent how to write a pull request description for your branch and prepare it for GitHub. This guide is for developers and maintainers who want reviewer-friendly PR descriptions without writing each one from scratch. By the end you will know what the skill does, how to install it, how to ask for it in plain language, and what it needs and touches on your machine.

GitHub PR Description Writertailcallhq/forgecode · Apache-2.0

Quick start

  1. 1Download and unzip the skill. Download the ZIP from our page and unzip it so the skill folder contains SKILL.md.
  2. 2Place it in the skills folder. Move the folder into ~/.claude/skills/ for all projects, or into the project's .claude/skills/ for one project. Alternatively, upload it under Settings → Capabilities → Skills in the Claude apps.
  3. 3Confirm the prerequisites. Make sure git and the GitHub CLI (gh) are installed, gh is authenticated with GitHub, and the repository has an origin remote and a main or master branch.
  4. 4Commit your changes on a branch. Work on a feature branch with at least one commit ahead of main, since the skill stops if there is nothing to submit.
  5. 5Ask the agent in plain language. Request a PR or a PR description, for example by asking it to create a pull request for your changes.
  6. 6Review the description. Read the Summary, Changes and Testing sections, and check that nothing sensitive from the diff appears before the PR is created.

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file. The file holds instructions and templates that an AI agent reads when a task matches the skill's description. This skill is named github-pr-description and its description says it applies when you ask to create a PR, generate a PR description, make a pull request, or submit changes for review.

When triggered, the skill has the agent check your branch, read the commit messages and code changes against main, classify the change, and write a structured description. The skill is mainly a set of instructions and a template, and it describes using the GitHub CLI to create the PR.

  • Verifies there are commits to create a PR for (not on main or master, with commits ahead of main)
  • Reads commit messages, a diff summary and the full diff against origin/main
  • Classifies the change as fix, feature, performance, refactor, docs, test or chore
  • Writes a description with Summary, Context, Changes, Use Cases, Testing and Links sections

Install the GitHub PR Description skill

Download the ZIP file for the skill from our page and unzip it. Then place the skill folder in one of two locations, depending on whether you want it for all projects or one project.

You can also upload the skill in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload the skill there.

  • All your projects: unzip into ~/.claude/skills/
  • One project only: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload the skill

Check the requirements before you use it

The skill depends on several tools and on your repository setup. If any of these are missing, the skill will not work as described.

The source lists git, the GitHub CLI (gh), a repository with an origin remote and a main or master branch, and GitHub authentication for gh. The git commands in the skill compare your branch with origin/main, so a branch with a different main name may need manual adjustment.

  • git installed
  • GitHub CLI (gh) installed
  • A repository with an origin remote and a main or master branch
  • GitHub authentication set up for gh
  • Your repository hosted on GitHub
git branch --show-current git log origin/main..HEAD --oneline

How do you trigger the skill with a natural request?

You do not need a special command. Describe what you want in ordinary language while you are on your feature branch. Requests that match the skill's description include asking the agent to create a PR, generate a PR description, make a pull request, or submit changes for review.

The agent will first check that there is something to send. If you are on main or master, or there are no commits ahead of main, it will tell you there is nothing to create a PR for.

  • 'Create a PR for my changes.'
  • 'Generate a PR description for this branch.'
  • 'Make a pull request and submit these changes for review.'
  • 'Write a description for the commits I made today.'

What does the generated description look like?

The skill asks for a fixed structure so reviewers see the same sections every time. The Summary is one sentence on what the PR does and why it matters. Context covers the problem being solved. Changes lists high-level changes. Testing gives steps reviewers can follow.

The guidelines in the skill discourage empty descriptions, placeholder text such as Fixes #(issue), file-by-file breakdowns unless necessary, and boilerplate. If your team uses its own PR template, check the output against it before submitting.

  • Summary, Context, Changes (with Key Implementation Details for complex work), Use Cases, Testing, Links
  • Change type is chosen from fix, feature, performance, refactor, docs, test or chore
  • Large diffs are sampled to the most meaningful files rather than read in full
## Summary [One sentence explaining what this PR does and why it matters] ## Context [Background information, related issues, previous work, or the problem being solved] ## Changes [High-level description of what changed] ## Testing [How to test the changes - step-by-step instructions]

Safety notes: scripts, network and sensitive diffs

According to the listing, this skill runs no scripts and does use the network. The GitHub CLI sends the pull request to GitHub, so the description and what it summarises are shared with that remote service.

The agent reads the full diff to write the description. Do not use the skill when the diff contains sensitive material that should not go to a remote service. Review the description before the agent submits it if you are unsure what the diff contains.

  • Runs scripts: no
  • Uses network: yes
  • The agent reads the full diff, so keep secrets and private data out of the branch before asking
  • For very large diffs, the skill samples key files rather than reading everything

What people use it for

  • A solo maintainer preparing a bug fix for review, where the agent classifies it as fix and explains the problem in Context.
  • A team that uses a standard PR template with summary, context, changes and testing sections, so every PR follows the same layout.
  • A developer who makes several commits on a feature branch and wants one description that covers the whole change against main.

Frequently asked questions

How do I install the GitHub PR Description agent skill?

Download the ZIP from our page and unzip it. Put the folder in ~/.claude/skills/ for all projects, or in a project's .claude/skills/ folder for one project. In the Claude apps you can also upload it under Settings → Capabilities → Skills.

What do I need to run the github-pr-description skill?

You need git, the GitHub CLI (gh) with GitHub authentication, and a repository with an origin remote and a main or master branch. The repository must be hosted on GitHub, since the skill relies on the GitHub CLI.

Is the GitHub PR Description skill free?

The skill is listed under the Apache-2.0 licence. The source does not mention pricing, so check the licence text for the terms that apply to your use.

Does the skill run scripts or send data over the network?

According to the listing, it runs no scripts and does use the network. The agent reads the full diff and the GitHub CLI sends the pull request to GitHub, so avoid it for diffs with sensitive material.

Why does the skill say there is nothing to create a PR for?

It checks that you are not on main or master and that there are commits ahead of origin/main. Commit your changes on a feature branch first, then ask again.

Can I use the skill if my main branch is not called main or master?

The git commands in the skill assume origin/main, so a branch with a different name may need adjusting. The listing notes the agent may need changes in that case.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are a developer, team or solo maintainer on GitHub who wants consistent, reviewer-friendly PR descriptions and has git and the GitHub CLI set up. Pick something else if your code is not on GitHub, your main branch has a different name, or your diffs contain material that must not be sent to a remote service.

Download the skill