skills.rest
simonwjackson
simonwjacksonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

se-commit-push-pr

Generate PR descriptions from commit history and diffs, then push and create pull requests.

Updated May 7, 2026
Search Tags:#automation#git#workflow#commit#pull-request#pr-description
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-commit-push-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: se-commit-push-pr
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-commit-push-pr
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-commit-push-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates turning a developer's working changes into a structured, ready-to-open pull request complete with a descriptive PR body tailored to the change and project conventions.

Core Features & Use Cases

  • Generate PR titles and bodies from the commit history and diff, aligned with repo conventions.
  • Push commits to a feature branch and open a PR, or refresh an existing PR description.
  • Support adaptive descriptions that scale with change complexity and provide an evidence section when applicable.

Quick Start

Run se-commit-push-pr on your current branch to generate a PR description, push commits, and open a pull request with an adaptive description.

Frequently Asked Questions about se-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 git commit history and diffs?▼

Automate PR description generation by analyzing commit history and diffs to create a structured narrative. This aligns the pull request body with project conventions, pushing commits to a feature branch and opening a ready-to-review PR.

Can I update an existing PR description using conventional commits?▼

Yes, you can refresh an existing PR description using conventional commits. The automation reads the latest commit history and diffs on your feature branch to update the pull request body adaptively without opening a duplicate PR.

What is the best way to automate pull request creation for a feature branch workflow?▼

Automating pull request creation for a feature branch workflow is best handled by generating titles and bodies directly from commit history. This ensures the PR scales adaptively with change complexity and follows established project conventions.

Does PR description automation work with complex changes that require an evidence section?▼

Yes, PR description automation works with complex changes by providing adaptive descriptions that scale with change complexity. It automatically includes an evidence section when applicable, derived from the git diff analysis.

Do I need to follow conventional commits to automate my git workflow?▼

Following conventional commits is required to properly automate your git workflow. The PR generation relies on commit messages and diffs to create a structured, ready-to-open pull request that aligns with repository conventions.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
diShine-digital-agencydiShine-digital-agency
1

shine-ship

Automate the ship cycle from branch creation to merged pull request.

Community
Intermediate
cipherstashcipherstash
17

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

Official
Intermediate
doitiandoitian
14

create-pr

Create pull requests with gh across branches and return the PR URL.

Community
Advanced