pr-assistant

Analyze code diffs and generate structured pull request drafts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/atman-33/skills --skill pr-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-assistant
Source: https://github.com/atman-33/skills/tree/main/skills/pr-assistant
Command: npx skills add https://github.com/atman-33/skills --skill pr-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams craft comprehensive pull requests by analyzing code changes, summarizing diffs, and generating structured PR drafts that can be reviewed and approved before submission.

Core Features & Use Cases

  • Analyzes the current branch diff against a target branch and summarizes changes by category (backend, frontend, docs, etc.).
  • Generates a PR draft with a structured summary, changes breakdown, related issues, and a testing checklist.
  • Provides an editable PR body ready for review or manual submission.

Quick Start

Use the pr-assistant to draft a PR description for the current branch against main, then review and customize before submission.

Frequently Asked Questions about pr-assistant

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

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

To generate a pull request description from code changes, the Skill analyzes your branch diff against a target branch, categorizes the changes, and auto-fills a structured PR draft. It summarizes diffs by category like backend, frontend, and docs.

What is the best way to draft a PR from a git diff?

The best way to draft a PR from a git diff is to use automated change analysis that extracts commit messages and categorizes modifications. This generates an editable PR body with a summary, changes breakdown, related issues, and a testing checklist.

Can I review and customize a PR draft before submission?

Yes, you can review and customize the PR draft before submission. The Skill provides an editable PR body that is ready for manual review, allowing you to adjust the structured summary and testing checklist before finalizing.

How does change analysis categorize code modifications for a pull request?

Change analysis for a pull request categorizes code modifications by summarizing diffs into distinct groups such as backend, frontend, and docs. This structured breakdown helps reviewers quickly understand the scope of the changes.

What should a structured pull request draft include?

A structured pull request draft should include a summary of changes, a categorized breakdown of diffs, related issues, and a testing checklist. This ensures comprehensive documentation for teams to review before approving the submission.