pr-writer

Generate GitHub pull request descriptions from branch changes and git history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the uncertainty and inconsistency of writing GitHub pull request descriptions by guiding users through a structured review-focused workflow.

Core Features & Use Cases

  • PR Description Generation: Creates concise reviewer-facing pull request titles and descriptions based on actual code changes and repository context.
  • PR Refresh Workflow: Helps update existing pull requests after material changes while keeping titles and bodies aligned with the current diff.
  • Use Case: A developer finishing a feature branch can use this Skill to analyze commits, review changes, and prepare a clear draft pull request for collaborators.

Quick Start

Ask the pr-writer skill to create or refresh a GitHub pull request description from the current branch changes.

Frequently Asked Questions about pr-writer

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

FAQPage Schema
How do I generate a GitHub pull request description from my code changes?

To generate a GitHub pull request description, this Skill analyzes your git history and branch diffs to create reviewer-facing titles and summaries aligned with repository conventions. It requires GitHub CLI authentication to inspect commits and verify branch state.

What's the best way to update an existing pull request after new commits?

To update an existing pull request after new commits, use the PR refresh workflow to re-analyze the current diff and regenerate titles and descriptions. This ensures the PR metadata stays aligned with the latest code changes on your feature branch.

Do I need GitHub CLI authentication to create pull request descriptions?

Yes, GitHub CLI authentication is required to create pull request descriptions. The Skill depends on GitHub CLI access to verify your branch state, inspect code diffs, and generate accurate PR metadata based on actual repository changes.

Can I use this Skill to analyze git history and prepare a draft pull request?

Yes, you can use this Skill to analyze git history, review code changes on a feature branch, and prepare a clear draft pull request. It guides a structured review-focused workflow to generate concise descriptions for collaborators.

How does the pull request description generation process work?

The pull request description generation process works by inspecting your branch diffs and commit history through GitHub CLI to extract meaningful code changes. It then structures these changes into a reviewer-facing format that aligns with repository conventions.

When do I need to refresh a GitHub pull request description?

You need to refresh a GitHub pull request description when material changes are pushed to an existing feature branch. The PR refresh workflow updates the title and body to match the current diff, preventing outdated information from reaching reviewers.