Git Pushing

This automates the full git workflow when you're ready to push code: it stages everything, generates a conventional commit message, and pushes to remote with proper upstream tracking. The real value is in the smart_commit.sh script that handles the boilerplate so you don't have to context switch between coding and remembering commit conventions. It triggers when you say things like "push this" or "save to github", which feels natural when you've just wrapped up work. One thing to note: it's marked critical risk because it's writing to your repo, so you'll want to review what's being committed. Community contributed, ships with the automation script included.

skills.sh installs: 810
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill git-pushing --agent claude-code

Installs into .claude/skills of the current project.

Files

Git Push Workflow

Stage only intended changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

Explicitly asks to push changes ("push this", "commit and push")
Mentions saving work to remote ("save to github", "push to remote")
Completes a feature and wants to share it
Says phrases like "let's push this up" or "commit these changes"

Safety Gates

Before staging, inspect git status --short --branch, confirm the intended files, and fetch the upstream branch when a concurrent push is plausible. Do not absorb unrelated dirty files.

Read repository policy before choosing the destination branch. If main or master is protected, or the repository defines a maintainer command such as merge:batch, create or use a topic branch and finish through the required pull-request checks. A user request to “push to main” describes the desired final state; it does not authorize bypassing server-side protection. Never keep retrying a direct push after a protected-branch rejection.

SKILL.md on GitHub