skills.rest
Kevin-Mok
Kevin-MokCOMMUNITY
Explore all skills by this author →
Website𝕏@Kev_MokGitHub

commit-push

Validate the working tree, stage intended files, and push conventional commits.

Updated Aug 27, 2026
Search Tags:#automation#git#commit#push#code-review#version-control
One-click install
npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill commit-push-kevin-mok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/Kevin-Mok/ai-cli-dotfiles/tree/main/dot_agents/skills/commit-push
Command: npx skills add https://github.com/Kevin-Mok/ai-cli-dotfiles --skill commit-push-kevin-mok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit-push automates the safe finalization of work in a git repository by ensuring changes are properly scoped, verified, and shipped, preventing unverified commits and accidental leaks of work-in-progress.

Core Features & Use Cases

  • Validates repository state (current branch, upstream) before staging anything
  • Runs minimal, deterministic checks and enforces the Readme gate via readme-recruiter-sync
  • Stages only the intended files or hunks, ensuring coherent, reviewable changes
  • Creates a conventional commit message and provides a clear, auditable history
  • Pushes the branch to the configured upstream automatically after a successful commit
  • Includes guardrails to prevent risky history rewrites or mixed changes

Quick Start

Prompt the AI to execute the commit-push workflow on the current session to verify, commit, and push the active branch.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I safely automate git commit and push without shipping unverified code?▼

To safely automate a git commit and push, the workflow validates the working tree, enforces staging discipline, and runs quality checks before finalizing changes. This prevents accidental leaks of work-in-progress and unverified commits.

How do I generate conventional commit messages automatically before pushing a branch?▼

Generating conventional commit messages automatically requires a process that scopes staged files or hunks into coherent changes. The workflow then creates an auditable commit message and pushes the branch to the configured upstream automatically.

Can I use automation to commit and push changes across typical software projects?▼

Yes, you can use automation to commit and push changes across typical software projects. The workflow applies when explicitly asked to ship session changes, validating the repository state and enforcing minimum quality gates regardless of the specific project.

What guardrails exist to prevent risky history rewrites during automated git pushes?▼

Guardrails to prevent risky history rewrites include enforcing staging discipline and blocking mixed changes. The workflow validates the current branch and upstream configuration, ensuring only properly scoped and verified changes are pushed automatically.

How does a README gate work when finalizing git commits?▼

A README gate works by enforcing documentation synchronization before allowing a commit to finalize. The workflow validates the README via readme-recruiter-sync as a minimum quality gate, ensuring documentation matches the shipped changes.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

git-commit

Analyze git diffs to generate conventional commit messages and stage files.

Official
Intermediate
D0NMEGAD0NMEGA
8

gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

Community
Advanced
cropsggcropsgg
15

pre-commit-setup

Install Husky and configure lint-staged for staged-file checks.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic