git-commit-push-pr

Automate git commits, branch management, and GitHub pull request creation.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill git-commit-push-pr-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/git-commit-push-pr
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill git-commit-push-pr-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often write generic or missing PR descriptions that fail to communicate the value and intent of their changes, forcing reviewers to reconstruct context from diffs alone. This Skill automates the entire journey from working tree changes to an open pull request while generating descriptions that adapt in depth and structure to match the actual complexity of the change.

Core Features & Use Cases

  • Adaptive PR Descriptions: Generates descriptions proportional to change complexity, from concise one-liners for typo fixes to full narratives with diagrams for architectural changes.
  • Complete Git Workflow: Handles branch creation, logical commit grouping, conventional commit messages, pushing, and PR creation or update.
  • Smart State Handling: Detects existing PRs, handles detached HEAD states, resolves base branches across forks, and classifies fix-up commits to keep descriptions focused on end results.

Quick Start

Use the git-commit-push-pr skill to turn your working tree changes into an open pull request with an adaptive description that matches the complexity of your work.

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 automate creating a GitHub pull request from local changes?

Automate creating a GitHub pull request from local changes by using a workflow that handles branch creation, logical commit grouping, pushing, and PR creation. This requires the GitHub CLI for pull request operations and git for version control.

How do I generate adaptive PR descriptions that scale with code complexity?

Generate adaptive PR descriptions that scale with code complexity by analyzing the diff to produce concise one-liners for small fixes and full narratives with diagrams for architectural changes, ensuring reviewers understand the change intent without reconstructing context.

How do I handle a detached HEAD state when pushing a branch to GitHub?

Handle a detached HEAD state when pushing a branch to GitHub by utilizing smart state handling features that detect the detached state, resolve the correct base branch across forks, and automatically manage branch creation before committing and pushing your changes.

Can I update an existing pull request instead of creating a new one?

Yes, you can update an existing pull request instead of creating a new one. The workflow detects existing PRs, classifies fix-up commits to keep descriptions focused on end results, and pushes new commits directly to the existing branch to update the PR.

Do I need the GitHub CLI installed to create pull requests from the command line?

Yes, you need the GitHub CLI installed to create pull requests from the command line. The automation requires the `gh` tool specifically for PR operations, alongside standard git for local version control and branch management.

What is the best way to group working tree changes into logical commits?

The best way to group working tree changes into logical commits is to use an automated workflow that evaluates your diffs, categorizes related modifications, and applies conventional commit messages before pushing the structured changes to GitHub.