managing-git-workflow

Automate git commits, pushes, and pull request creation for local GitHub repositories.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/ether-moon/skill-set --skill managing-git-workflow-ether-moon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-git-workflow
Source: https://github.com/ether-moon/skill-set/tree/main/plugins/skill-set/skills/managing-git-workflow
Command: npx skills add https://github.com/ether-moon/skill-set --skill managing-git-workflow-ether-moon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the multi-step, error-prone process of creating context-aware git commits, pushing branches, and opening pull requests so developers can spend less time on repository housekeeping and more on delivering code.

Core Features & Use Cases

  • Context-aware commit messages: Generate commit messages based on recent commit patterns, diff summaries, and ticket numbers extracted from branch names.
  • Safe push and PR workflows: Automatically commit uncommitted changes, push branches with proper upstream handling, detect existing PRs, and create new PRs with generated titles and descriptions using the gh CLI.
  • Real-world use case: Turn a local feature branch with staged or unstaged changes into a pushed branch and an opened GitHub pull request with a summarized description and test checklist.

Quick Start

Use the managing-git-workflow skill to generate a commit message for current changes, push the current branch to origin, and open a pull request with a generated title and description.

Frequently Asked Questions about managing-git-workflow

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

FAQPage Schema
How do I automate git commits, pushes, and pull request creation in GitHub?

You can automate git commits, pushes, and pull requests by running combined Bash git and gh commands to handle uncommitted changes, push branches with upstream tracking, and open PRs using generated titles and descriptions.

How does generating commit messages from branch names work?

Generating commit messages works by analyzing recent commit patterns and diff summaries, then automatically extracting ticket numbers from local branch names to create context-aware commit messages for your repository.

Do I need the gh CLI to open a pull request from a local branch?

You need optional gh CLI authentication to open a pull request from a local branch. The workflow requires local git repository access and uses the gh CLI to detect existing PRs and create new ones with summarized descriptions.

What is the best way to handle uncommitted changes before pushing a branch?

The best way to handle uncommitted changes before pushing is to automatically stage and commit both staged and unstaged modifications, ensuring your local feature branch is clean prior to executing the upstream push.

Can I detect existing pull requests before creating a new one?

Yes, you can detect existing pull requests before creating a new one. The workflow checks for existing PRs on your branch using gh CLI commands to prevent duplicate pull request creation on GitHub.

What happens if my local branch lacks upstream tracking during a push?

If your local branch lacks upstream tracking, the workflow automatically configures proper upstream handling during the push to ensure your local branch correctly links to the remote origin repository.