Git Pushing
- 876 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
git-pushing is an agent skill that stages all changes, generates a conventional commit, and pushes to a remote GitHub branch for developers who need a reliable one-command git publish workflow.
About
git-pushing is a Claude Code agent skill from sickn33/antigravity-awesome-skills that automates the end-to-end git publish loop: stage all changes, draft a conventional commit message, and push to the current remote branch. The skill is marked critical risk because it runs real git and network operations against your repository. Developers reach for git-pushing when they say push this, commit and push, save to github, or finish a feature and want it on the remote without manually chaining git add, git commit, and git push. It is designed for explicit user intent rather than silent auto-commits during exploratory edits.
- Automatically stages all changes before committing
- Enforces conventional commit format with Claude footer
- Runs exclusively via the provided smart_commit.sh script
- Handles branch push with upstream tracking (-u flag)
- Activates on explicit push requests or feature completion signals
Git Pushing by the numbers
- 876 all-time installs (skills.sh)
- +24 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #74 of 739 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill git-pushingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 876 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 1 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you commit and push with conventional commits?
Reliably stage changes, generate conventional commits, and push to a remote GitHub branch with one command.
Who is it for?
Developers who want a single guarded workflow to stage, conventional-commit, and push when they explicitly ask to publish work.
Skip if: Teams that require interactive staging, signed commits, or pull-request-only flows without direct branch pushes.
When should I use this skill?
The user explicitly asks to push, commit and push, save work to GitHub, or share a completed feature on the remote branch.
What you get
Staged changes, a conventional commit on the local branch, and an updated remote GitHub branch.
- conventional commit
- pushed remote branch
Files
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 skills/git-pushing/scripts/smart_commit.shWith custom message:
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"
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.264k92.8k
Git Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.164k187kResolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.160k187k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.145k261k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.2k37k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.15.6k147How it compares
Pick git-pushing when you want a single explicit publish command; use granular git skills when you need selective staging or PR-only review gates.
FAQ
When should git-pushing run?
git-pushing should run when a developer explicitly asks to push, commit and push, save to GitHub, or publish a finished feature to the remote branch. The skill is not meant for silent commits during exploratory edits.
What does git-pushing do in one step?
git-pushing stages all changes, writes a conventional commit message, and pushes to the remote branch on GitHub. The workflow replaces manually chaining git add, git commit, and git push.
Is Git Pushing safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.