skills.rest
dudqks0319-cpu
dudqks0319-cpuCOMMUNITY
Explore all skills by this author →
GitHub

git_pushing

Automates Git commits and pushes with user approval and conventional commit messages.

Updated Jan 16, 2026
Search Tags:#automation#git#version control#commit#conventional commits#github#push
One-click install
npx skills add https://github.com/dudqks0319-cpu/antigravity-skills --skill git-pushing-dudqks0319-cpu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git_pushing
Source: https://github.com/dudqks0319-cpu/antigravity-skills/tree/main/git_pushing
Command: npx skills add https://github.com/dudqks0319-cpu/antigravity-skills --skill git-pushing-dudqks0319-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing changes, writing consistent commit messages, and pushing to remote repositories is repetitive and error-prone. This Skill streamlines the entire Git commit-and-push workflow while keeping you in control through an approval step. ## Core Features & Use Cases - Change Summary: Runs git status to inspect modified files and reports a concise summary of what changed before committing. - Conventional Commit Messages: Generates structured commit messages using standard prefixes like feat, fix, docs, style, and refactor. - Approval Gate: Requires explicit user confirmation before executing any commit or push, preventing accidental uploads to remote repositories. - Use Case: After finishing a dark mode feature, simply ask to commit and push; the Skill summarizes the edited HTML and CSS files, proposes the message "feat: add dark mode support", and waits for your approval before pushing to GitHub. ## Quick Start Ask the assistant to commit and push your current changes to GitHub, then approve the proposed commit message.

Frequently Asked Questions about git_pushing

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

FAQPage Schema
How do I automate Git commits and pushes safely?▼

Use a workflow that first runs git status to summarize changed files, proposes a commit message, and waits for your explicit approval before committing and pushing. This prevents accidental uploads of unfinished work to remote repositories.

What is the conventional commit message format?▼

Conventional commits use a type prefix followed by a description, such as "feat: add login page" or "fix: resolve null pointer error". Common types include feat for features, fix for bug fixes, docs for documentation, style for formatting, and refactor for code restructuring.

Can I push to GitHub without reviewing changes first?▼

This Skill enforces a review step by design: it always shows a change summary and proposed commit message, then requires your approval before pushing. This security rule cannot be skipped, protecting you from pushing unintended changes.

Why should I check git status before committing?▼

Running git status reveals which files are modified, staged, or untracked, so you can catch unintended changes like debug files or secrets before they enter the commit history. It is a standard safeguard in any commit workflow.

What are the limitations of automated Git commit messages?▼

Automatically proposed messages may not capture the full intent behind complex changes spanning many files. Review and edit the suggested message during the approval step to ensure it accurately describes the change for future readers.

Related Skills

Explore More Software Engineering Skills→
codeaholicguycodeaholicguy
1.6k

dev-commit

Creates verified conventional git commits containing only intended changes.

Community
Intermediate
maxbeaudoinmaxbeaudoin

open-pr

Push the current branch, open a GitHub PR, wait for CI, and squash-merge into main.

Community
Advanced
v1truv1usv1truv1us
7

git-worktree

Create, list, and remove Git worktrees for parallel development.

Community
Intermediate
luanluan
4

git-surgeon

Perform hunk-level Git operations including staging, unstaging, discarding, and commit splitting.

Community
Intermediate