commit-push

Automate git commits and pushes with strict message format enforcement.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/kkn1125/devkimson-skills --skill commit-push-kkn1125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/kkn1125/devkimson-skills/tree/main/skills/commit-push
Command: npx skills add https://github.com/kkn1125/devkimson-skills --skill commit-push-kkn1125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and standardizes the commit and push process in git, enforcing a main-only branch workflow, all-visible-changes staging, and the required emoji/type commit message format, thus improving consistency and efficiency in code contributions.

Core Features & Use Cases

  • Automated Commit Workflow: Facilitates the automatic commit of all visible changes from git status --short.
  • Commit Message Format Adherence: Ensures that each commit follows a strict message format that includes emoji and short English type.
  • Branch and Safety Rule Enforcement: Implements rules for branch usage and safety to protect the main branch and maintain code integrity.

Quick Start

Execute the 'commit-push' command to automatically commit and push all visible changes from the current git status to the 'main' branch.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I automate git commit and push for all modified files?

To automate git commit and push for all modified files, this Skill stages all visible changes from `git status --short` and pushes them to the remote repository automatically. It streamlines the entire commit workflow by enforcing a main-only branch strategy and strict commit message formatting.

What is the required commit message format for enforcing standardization?

The required commit message format for enforcing standardization mandates the inclusion of a specific emoji and a short English type prefix. This strict format adherence ensures consistency and clarity in code contributions across the software development environment.

Can I use this automated git commit workflow on branches other than main?

You cannot use this automated git commit workflow on branches other than main. The Skill explicitly enforces a main-only branch workflow to protect code integrity and maintain standardized branch usage across the project.

Does this commit and push automation stage specific files or all visible changes?

This commit and push automation stages all visible changes. It automatically detects modifications using `git status --short` and stages every visible change before committing and pushing, rather than allowing selective file staging.

Why enforce a main branch workflow for automated git pushes?

Enforcing a main branch workflow for automated git pushes protects the main branch and maintains code integrity. It implements safety rules and standardizes the commit process, ensuring consistent code contributions and preventing unauthorized branch usage.