git-pushing

Stage all changes, generate conventional commit messages, and push to remote branches.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mbcoalson/skills --skill git-pushing-mbcoalson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pushing
Source: https://github.com/mbcoalson/skills/tree/main/.claude/skills/git-pushing
Command: npx skills add https://github.com/mbcoalson/skills --skill git-pushing-mbcoalson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the repetitive and often error-prone process of staging, committing with conventional messages, and pushing Git changes. It ensures consistent commit hygiene and simplifies the developer workflow, especially for new branches or complex commit types.

Core Features & Use Cases

  • Automated Staging & Committing: Stages all changes and generates conventional commit messages (e.g., feat:, fix:, docs:, test:, chore:).
  • Claude Footer Integration: Automatically adds a "Generated with Claude Code" footer to commits.
  • Smart Pushing: Handles new branches by automatically using the -u flag for the first push and detects SSH URL rewrites.
  • Use Case: "Commit all my changes with a 'feat: add new user authentication' message and push to the remote repository."

Quick Start

Commit all my changes with a 'feat: add new user authentication' message and push to the remote.

Frequently Asked Questions about git-pushing

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

FAQPage Schema
How do I automate staging, committing, and pushing Git changes?

Automated staging, committing, and pushing consolidates your workflow into one step. The Skill stages all changes, generates a conventional commit message based on the diff, adds a Claude Code footer, and pushes to the remote branch—handling first-push scenarios and SSH rewrites automatically.

What are conventional commits and why should I use them?

Conventional commits follow a standard format (feat:, fix:, docs:, test:, chore:) that makes commit history readable and enables automated tooling. They ensure consistent commit hygiene across your repository and simplify tracking what changed and why.

How does the Skill handle pushing a new branch for the first time?

When pushing a new branch, the Skill automatically applies the `-u` flag to set up upstream tracking, eliminating manual configuration. This establishes the connection between your local and remote branches in one operation.

Can I use this Skill if I haven't made any commits yet?

The Skill detects edge cases like repositories with no commits and handles them gracefully. It stages your initial changes and creates your first conventional commit with proper formatting before pushing.

Does the Skill work with SSH Git URLs?

Yes. The Skill detects and handles SSH URL rewrites automatically, so you can push securely without manual intervention or configuration adjustments.

What happens if I want to push work after finishing a feature?

Stage all your feature changes and push as a single operation. The Skill analyzes your diff, generates a feat: commit message, and pushes to your branch—capturing your completed work in one deterministic workflow.