pr-writer

Generate and update GitHub pull request descriptions using the GitHub CLI.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill pr-writer-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/pr-writer
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill pr-writer-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This skill eliminates the inconsistency and manual effort involved in writing high-quality, professional pull request descriptions that adhere to strict engineering standards.

Core Features & Use Cases

  • Standardized Formatting: Enforces conventional commit-based titles and structured, reviewer-focused descriptions.
  • Automated Context Gathering: Uses GitHub CLI to analyze branch diffs and existing PR state to generate accurate, up-to-date summaries.
  • Use Case: When you have completed a complex feature, use this skill to automatically generate a PR description that highlights the technical impact and rationale, ensuring your reviewers have all the necessary context without manual drafting.

Quick Start

Use the pr-writer skill to analyze the current branch and generate a professional pull request description for the pending changes.

Frequently Asked Questions about pr-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request descriptions for GitHub branches?

You can automate pull request descriptions by using this skill to analyze your branch diffs and generate standardized, reviewer-focused summaries automatically. It leverages the GitHub CLI to gather context and update PR state without manual drafting.

What is the best way to standardize GitHub PR formatting across a team?

The best way to standardize PR formatting is to enforce conventional commit-based titles and structured descriptions. This skill automates that process by generating consistent, high-quality documentation for code changes and peer reviews.

Do I need the GitHub CLI configured to automate code review documentation?

Yes, you need the GitHub CLI (gh) authenticated and configured for repository interaction. The skill relies on gh to analyze branch diffs, gather context, and update existing pull request states accurately.

Can I update an existing GitHub pull request description automatically?

Yes, you can update an existing GitHub pull request description automatically. The skill analyzes the current branch diff and existing PR state to generate accurate, up-to-date summaries for your reviewers.

How does automated PR context gathering work for complex features?

Automated PR context gathering works by using the GitHub CLI to analyze branch diffs and existing PR state. This generates accurate summaries that highlight technical impact and rationale, ensuring reviewers have necessary context.

When should I avoid using automated pull request writers?

You should avoid using automated pull request writers if your repository is not hosted on GitHub or if the GitHub CLI is not authenticated. The skill specifically requires gh configured for repository interaction to function properly.