git-commit-push-pr

Generate adaptive pull request descriptions from Git branch changes.

2|1|Updated Apr 17, 2026

Search Tags:#automation #git #workflow #commit #code-review #pull-request #pr-description

Ready to run

npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill git-commit-push-pr-wangrenzhu-ola

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/git-commit-push-pr
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill git-commit-push-pr-wangrenzhu-ola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a set of working changes into a clear, value-driven PR description that helps reviewers understand impact without drafting from scratch.

Core Features & Use Cases

Adaptive PR descriptions that scale with the complexity of the change and the intended audience.
Support for creating a new PR or rewriting an existing PR description to refresh context and evidence.
Seamless alignment with commit/push workflows to ensure PRs consistently reflect the latest work and reasoning.
Use Case: A developer finishes a feature and wants a concise PR description that communicates user-facing impact and technical changes.

Quick Start

Generate a PR description for your current branch changes.

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 pull request description from git commit history?▼

To generate a pull request description, the Skill analyzes your git commit history and working changes to produce value-driven summaries. It scales the description length based on change complexity and branch context, ensuring reviewers understand the impact without manual drafting.

Can I update an existing PR description to reflect new commits?▼

Yes, you can update an existing PR description by requesting a rewrite. The Skill refreshes the context and evidence while preserving existing evidence blocks where present, ensuring your pull request consistently reflects the latest work and reasoning.

How to write a PR description that scales with change complexity?▼

Writing a PR description that scales with change complexity requires evaluating the branch context and technical impact. This Skill generates adaptive descriptions that align with conventional commit conventions, applying clear value-first narration for both small fixes and complex features.

Does this PR description generator work with conventional commit workflows?▼

Yes, this PR description generator works with conventional commit workflows by following conventional commit-oriented conventions when possible. It aligns your commit and push workflows to ensure pull requests consistently reflect the latest work and technical reasoning.

What is the best way to automate PR description creation for code review?▼

The best way to automate PR description creation for code review is using a Skill that parses working changes and generates value-first narration. It eliminates manual drafting, preserves existing evidence blocks, and communicates user-facing impact to reviewers.

When should I not use automated PR description generation?▼

You should not use automated PR description generation when your changes lack clear commit context or require highly customized, non-conventional formatting. The Skill follows conventional commit-oriented conventions and preserves existing evidence blocks, so highly irregular workflows may not yield optimal descriptions.