commit-push

Commit staged changes and push to the current upstream branch.

3|2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/wzh4464/claude-skills --skill commit-push-wzh4464
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/wzh4464/claude-skills/tree/main/commit-push
Command: npx skills add https://github.com/wzh4464/claude-skills --skill commit-push-wzh4464

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit staged/unstaged changes and push to the remote branch in a single workflow.

Core Features & Use Cases

  • End-to-end Git commit and push automation for the current branch
  • Safe staging by file name (avoids accidental broad adds) and automatic secret/file exclusion
  • Enforces commit message convention (JS-XXXX: short description) and co-authored trailer
  • Pushes to the current upstream, reporting the resulting commit hash

Quick Start

Instruct the tool to stage the desired changes, commit with a standard message, and push to the current upstream branch.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I commit staged changes and push to a remote branch in one step?

To commit and push in one step, this workflow stages files by name, commits with a JS-XXXX message, and pushes to the current upstream branch, returning the final commit hash.

Does this git workflow automation enforce commit message conventions?

Yes, this git workflow automation enforces commit message conventions by requiring the JS-XXXX: short description format and appending a co-authored trailer before pushing to the remote.

Can I safely stage files for a commit and push workflow without adding secrets?

You can safely stage files for a commit and push workflow because it stages files by name to avoid accidental broad adds and automatically excludes secrets and sensitive files.

What is the best way to automate git pushes for small feature branch updates?

The best way to automate git pushes for small feature branch updates is using a workflow that commits staged changes and pushes directly to the current upstream branch in a single action.

Are there limitations when using one-step commit and push for version control?

A limitation of this one-step commit and push workflow is that it pushes only to the current upstream branch and requires the strict JS-XXXX commit message format, which may not suit all repositories.