commit-push-pr-workflow

Automate Git feature workflows from worktree setup through post-merge cleanup.

3|2|Updated Mar 14, 2026

Search Tags:#git #workflow #commit #branching #worktree #pr #pull-request

Ready to run

npx skills add https://github.com/wzh4464/claude-skills --skill commit-push-pr-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push-pr-workflow
Source: https://github.com/wzh4464/claude-skills/tree/main/commit-push-pr-workflow
Command: npx skills add https://github.com/wzh4464/claude-skills --skill commit-push-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the full lifecycle of feature development in a Git repository, handling setup, branching, commits, PRs, and post-merge cleanup to streamline collaboration.

Core Features & Use Cases

Worktree setup and isolation for feature work across environments.
Clear guidelines for branching, committing, PR creation, and merge hygiene.
Use Case: When starting a feature, spin up a separate worktree, create a feature branch, commit changes with descriptive messages, open a PR, and clean up after merge.

Quick Start

Create a feature branch from the default branch, set up a worktree if preferred, implement changes, commit with a descriptive message, push, open a pull request, and perform post-merge cleanup.

Frequently Asked Questions about commit-push-pr-workflow

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

FAQPage Schema

How do I manage a complete git feature workflow from branching to pull request?▼

To manage a complete git feature workflow, set up an isolated worktree, create a feature branch, commit changes with descriptive messages, push, open a pull request, and perform post-merge cleanup.

What is the best way to isolate feature development in git across different operating systems?▼

The best way to isolate feature development across Windows and Unix-like environments is using git worktrees, which keep branches in separate directories to streamline collaboration without cross-platform shell conflicts.

How do I clean up local branches and worktrees after a pull request merge?▼

After a pull request merge, clean up local branches and worktrees by removing the merged branch and deleting the associated worktree directory to maintain a tidy repository state.

Can I use shell-agnostic git commands for team workflows on both Windows and Unix?▼

Yes, you can use shell-agnostic git commands for team workflows on both Windows and Unix-like systems, ensuring cross-platform compatibility for worktree setup, branching, and pull request creation.

When do I need a git worktree for my feature branch?▼

You need a git worktree when starting a feature branch to isolate development work from your main repository, allowing simultaneous work on multiple branches without stashing current changes.

Does this git workflow handle commit messaging and PR creation automatically?▼

This git workflow provides guidance for commit messaging and PR creation, applying standard software development practices to ensure descriptive commits and proper merge hygiene throughout the feature lifecycle.