skills.rest
sred-ca
sred-caOFFICIAL
Explore all skills by this author →
GitHub

git-commit-push

Stage, commit, and push code changes to GitHub with generated commit messages.

Updated Apr 14, 2026
Search Tags:#automation#git#commit#github#push#version-control
One-click install
npx skills add https://github.com/sred-ca/AISalesCoach --skill git-commit-push-sred-ca
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push
Source: https://github.com/sred-ca/AISalesCoach/tree/main/.claude/skills/git-commit-push
Command: npx skills add https://github.com/sred-ca/AISalesCoach --skill git-commit-push-sred-ca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically manage changes by staging, committing, and pushing updates to GitHub, ensuring consistent history and reducing manual steps.

Core Features & Use Cases

  • Automatic staging: Stage all changes with git add -A, honoring the repository's .gitignore rules.
  • Smart commit messages: Generate concise commit messages from diffs and append a Co-Authored-By line.
  • Push with safeguards: Push to origin/main and, if necessary, rebase locally to accommodate remote changes.
  • Status reports: Inform the user of the committed changes and resulting commit hash.

Quick Start

Invoke the push command by saying '/push' to commit all changes and push to origin/main.

Frequently Asked Questions about git-commit-push

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

FAQPage Schema
How do I automatically commit and push code changes to GitHub?▼

To automatically commit and push changes to GitHub, you can invoke a push command that stages all modifications, generates a concise commit message from the diff, and pushes the updates to origin/main.

How are commit messages generated when automating git pushes?▼

Commit messages are generated by analyzing the code diff to derive a concise description of the changes, which is then appended with a Co-Authored-By line before pushing to the main repository.

Do I need a local Git repository configured with a remote to automate pushes?▼

Yes, automating pushes requires a local Git repository with a configured remote, access to the working tree, and a valid ignore setup to prevent sensitive files from being committed during staging.

What happens if there are remote changes on origin/main when I push?▼

When pushing to origin/main, the process includes safeguards to handle remote changes by rebasing locally if necessary, ensuring your local commits synchronize smoothly with the updated main branch.

Does automated git staging respect my .gitignore rules?▼

Yes, automated staging uses git add -A, which honors the repository's .gitignore rules to ensure ignored files are not included in the commit.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
thanh-abaiithanh-abaii
34

gs:land-and-deploy

Merge pull requests, run CI/CD pipelines, and verify production health.

Community
Advanced
UnsupervisedcomUnsupervisedcom
49

commit.commit_and_push

Commit and push validated code changes after lint passes.

Official
Basic
paulnsorensenpaulnsorensen
2

commit

Stage specific files and create conventional commits in Git.

Community
Intermediate