pr-writer

Parse git diffs and generate PR bodies from repository templates.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Bangjjack/Bangjjack-Frontend --skill pr-writer-bangjjack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/Bangjjack/Bangjjack-Frontend/tree/main/.cursor/skills/pr-writer
Command: npx skills add https://github.com/Bangjjack/Bangjjack-Frontend --skill pr-writer-bangjjack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR descriptions are often manually written and can miss required template sections, causing review friction and inconsistent documentation.

Core Features & Use Cases

  • Analyze git changes and generate a PR body that exactly adheres to the repository's pull_request_template.md.
  • Use for PR creation, drafting a PR description, or updating an existing PR after new commits.
  • Works across multiple commits and diffs to maintain a consistent PR narrative.

Quick Start

Run PR Writer after making changes to automatically generate a PR body that conforms to the template.

Frequently Asked Questions about pr-writer

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

FAQPage Schema
How do I automatically generate a PR body from a git diff?

To automatically generate a PR body, this Skill parses your git diff against the default branch and constructs a structured description. It builds the PR body using your repository's pull request template across a set of commits.

What is the best way to ensure my PR description follows the repository template?

The best way to ensure adherence is using a template parser that reads your pull_request_template.md and outputs a structured PR body. It automatically populates required sections like issue references, task items, and checklists.

Can I update an existing PR description after pushing new commits?

Yes, you can update an existing PR description after new commits. The tool works across multiple commits and diffs to maintain a consistent PR narrative, ensuring your updated PR body respects the exact template structure.

Does this PR template generator work for both bug fixes and feature development?

Yes, this PR template generator works for bug fixes, feature development, and documentation updates. It analyzes your specific git changes and constructs a PR body that follows the repository's predefined template structure and labels.

What should I do if my automated PR body is missing required checklist items?

If your automated PR body is missing checklist items, ensure your repository has a valid pull_request_template.md. The parser constructs the PR body by respecting the exact template structure and including any predefined checklists found.