skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit-push-pr

Generate PR descriptions from branch diffs and commit history.

434|33|Updated Jul 27, 2025
Search Tags:#automation#git#workflow#commit#pull-request#pr-description
One-click install
npx skills add https://github.com/udecode/kitcn --skill git-commit-push-pr-udecode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/git-commit-push-pr
Command: npx skills add https://github.com/udecode/kitcn --skill git-commit-push-pr-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically convert a developer's working changes into a PR description that communicates value and intent, reducing back-and-forth and ensuring reviewers understand the why behind the what.

Core Features & Use Cases

  • Generate a value-focused PR description from the full branch diffs and commit history.
  • Support updating existing PR descriptions to reflect new changes.
  • Align PR titles and bodies with project conventions and naming standards.

Quick Start

Describe your changes and let this skill generate a value-focused PR description.

Frequently Asked Questions about git-commit-push-pr

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

FAQPage Schema
How do I generate a PR description from local commits automatically?▼

You can generate a PR description by analyzing your full branch diff and commit history to produce value-focused notes that communicate the intent and rationale behind your changes.

What is the best way to update an existing PR description with new commits?▼

Updating an existing PR description involves processing new branch diffs to reflect the latest changes while maintaining alignment with your project's conventions and reviewer clarity.

Can I use this to format PR titles and bodies for different types of changes?▼

Yes, this skill formats PR titles and bodies for feature, bugfix, or refactor changes, ensuring the output follows your project conventions and emphasizes the value delivered to reviewers.

Does the generated PR description follow my project naming standards?▼

Yes, the generated PR description aligns with your project conventions and naming standards, ensuring both titles and bodies match the expected formatting for reviewer clarity.

Why do I need an automated workflow for writing PR descriptions?▼

An automated workflow reduces reviewer back-and-forth by ensuring reviewers understand the why behind the what, turning local commits into clear, value-first documentation.

When should I not use an automated pull-request description generator?▼

Avoid using an automated pull-request description generator when your branch lacks meaningful commit history or when changes require manual context that cannot be derived from the diff.

Related Skills

Explore More Software Engineering Skills→
Andresch2Andresch2

commit

Stage relevant changes and create Git commits and pull requests via GitHub CLI.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
1ambda1ambda
2

git-workflow

Automate Git commit messages, pull requests, and branch naming.

Community
Intermediate
carlos-algmscarlos-algms
2

create-pull-request

Generate GitHub pull request titles and bullet-only bodies via gh pr create.

Community
Intermediate