git-pushing

Stage changes, create conventional commits, and push to remote branches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates common Git operations by staging changes, creating conventional commits, and pushing to a remote branch, reducing manual steps and ensuring consistent commit messages.

Core Features & Use Cases

  • Automated staging & commit: Stages all changes and generates conventional commit messages following standard formats.
  • Smart messaging with Claude footer: Automatically appends a Claude Code footer and co-authorship for traceability.
  • Push workflows: Pushes to existing remote branches or creates new branches with -u when needed; suggests pull request link for GitHub remotes.

Quick Start

Use the git-pushing skill to commit and push your current changes with a single command, or rely on the script to handle it end-to-end.

Frequently Asked Questions about git-pushing

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

FAQPage Schema
How do I automate git commit and push with conventional commit messages?

You can automate git commit and push by running a dedicated script that stages all changes, generates conventional commit messages, and pushes to the remote branch. This reduces manual steps and ensures consistent commit history.

What is a conventional commit and how does an automated workflow apply it?

A conventional commit follows a standard format for commit messages. The automated workflow stages your changes and creates a commit message adhering to these formats, appending a Claude Code footer and co-authorship for traceability.

How do I push a new branch to a remote repository for the first time?

To push a new branch, the automated script uses the -u flag when pushing to the remote repository. This sets up the upstream tracking connection and suggests a pull request link if the remote is on GitHub.

Can I use this git workflow for both bug fixes and feature development?

Yes, the git workflow applies to feature work, bug fixes, and collaborative patches. It handles staging, commit message generation, and pushing regardless of the type of changes you are saving to the remote repository.

Do I need any external dependencies to automate staging and pushing changes?

No external dependencies are required to automate staging and pushing changes. The workflow relies entirely on a dedicated shell script to handle staging, commit generation, and push operations.