Git Pushing
Stage all changes, create a conventional commit, and push to the remote when you explicitly want work saved on GitHub or shared with collaborators.
Overview
Git Pushing is an agent skill for the Ship phase that stages changes, creates a conventional commit via smart_commit.sh, and pushes to the remote branch when you explicitly request it.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill git-pushingWhat is this skill?
- Mandatory smart_commit.sh script—no ad-hoc manual git command sequence
- Conventional commit messages with optional custom feat:/fix: prefix
- Handles staging, Claude footer, and push with -u upstream
- Triggers on explicit push, commit-and-push, or save-to-GitHub phrasing
- Community skill flagged critical risk—scope-bound to push workflow only
- 1 required script entry point: smart_commit.sh
Adoption & trust: 700 installs on skills.sh; 40.1k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished a feature but want one reliable, conventional commit and push without the agent improvising unsafe git commands.
Who is it for?
Indie devs using Claude Code or similar who want a single scripted commit-and-push ritual on demand.
Skip if: Selective partial commits, rebases, force-push, or release tagging—stop and use manual git when scope exceeds push-this.
When should I use this skill?
User explicitly asks to push, commit and push, save to GitHub/remote, completes a feature to share, or says let's push this up.
What do I get? / Deliverables
All staged changes land on the remote branch with a conventional message and upstream tracking after the script completes successfully.
- Conventional commit on current branch
- Remote branch updated with push -u
Recommended Skills
Journey fit
Commit-and-push is the handoff from local work to shared history—canonical shelf is Ship once changes are ready to leave your machine. Review subphase covers the git hygiene step after implementation and before or alongside broader launch checks.
How it compares
Opinionated bash workflow skill—not a general Git cheat sheet or PR description generator.
Common Questions / FAQ
Who is git-pushing for?
Solo builders in agent-driven repos who routinely end sessions with an explicit commit-and-push request and want script-enforced conventional commits.
When should I use git-pushing?
During Ship when you explicitly ask to push, commit and push, save work to GitHub or the remote, or say you completed a feature and want it shared.
Is git-pushing safe to install?
It performs real git writes and is rated critical risk; review the Security Audits panel on this page and read smart_commit.sh before granting shell and git access.
SKILL.md
READMESKILL.md - Git Pushing
# Git Push Workflow Stage all 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" ## Workflow **ALWAYS use the script** - do NOT use manual git commands: ```bash bash skills/git-pushing/scripts/smart_commit.sh ``` With custom message: ```bash bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature" ``` Script handles: staging, conventional commit message, Claude footer, push with -u flag. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. #!/bin/bash set -e # Default commit message if none provided MESSAGE="${1:-chore: update code}" # Add all changes git add . # Commit with the provided message git commit -m "$MESSAGE" # Get current branch name BRANCH=$(git rev-parse --abbrev-ref HEAD) # Push to remote, setting upstream if needed git push -u origin "$BRANCH" echo "✅ Successfully pushed to $BRANCH"