generate-pr

Generate a complete PR description from branch diffs and commits.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/selcukyucel/north-starr-genai --skill generate-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-pr
Source: https://github.com/selcukyucel/north-starr-genai/tree/main/skills/generate-pr
Command: npx skills add https://github.com/selcukyucel/north-starr-genai --skill generate-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate PR descriptions automatically by analyzing the changes in a branch and existing PR templates, saving time and ensuring consistency.

Core Features & Use Cases

  • Analyze the current branch to summarize changes and compile a PR body
  • Populate the PR template with commits, changed files, and diffs
  • Support usage across Git platforms and workflows
  • Use case: When finalizing a feature branch, produce a polished PR description ready to paste into a PR on GitHub, GitLab, or similar platforms.

Quick Start

Run the skill on the current repository to produce a complete PR description for the active branch.

Frequently Asked Questions about generate-pr

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

FAQPage Schema
How do I automatically generate a PR description from git commits and diffs?

Auto-generating a PR description works by analyzing the current branch's git commits and diffs, reading any optional project PR template, and outputting a ready-to-paste PR body. This ensures consistency across feature and fix branches.

Can I use an auto-generated pull request description with GitHub and GitLab?

Yes, auto-generated pull request descriptions work across Git platforms including GitHub and GitLab. The skill reads branch changes and optional PR templates to produce a platform-agnostic PR body ready to paste.

What's the best way to populate a PR template with changed files automatically?

The best way to populate a PR template automatically is to run a skill that gathers changed files and commits via git commands, then fills the template fields with the summarized diffs to create a complete PR body.

Do I need a PR template file to auto-generate pull request descriptions?

No, a PR template file is optional. The skill can generate a complete PR description from branch diffs and commits alone, but it will incorporate the template if one exists in the project to ensure consistent formatting.

How does analyzing branch diffs help write better pull request documentation?

Analyzing branch diffs helps write better pull request documentation by identifying all code changes and commits, then summarizing them into a structured PR description that captures the full scope of the feature or fix branch.