commit-push

Name: commit-push
Availability: InStock
Author: zytakeshi

Automate staging, committing, and pushing code changes with conventional commits.

1|1|Updated Mar 21, 2026

Search Tags:#automation #git #commit #ci-cd #pull-request #version-control

Ready to run

npx skills add https://github.com/zytakeshi/admin-skills --skill commit-push-zytakeshi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/zytakeshi/admin-skills/tree/main/skills/commit-push
Command: npx skills add https://github.com/zytakeshi/admin-skills --skill commit-push-zytakeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire commit workflow by analyzing repository changes, generating a high-quality conventional commit message, staging relevant files, committing, and pushing to the remote in one smooth sequence.

Core Features & Use Cases

Analyze git state (status, diff, diff --cached, log, branch) to determine changes that need to be committed and detect edge cases.
Generate conventional commits that reflect the intent and scope of changes, improving history readability.
Safely stage, commit, and push changes with guided prompts to avoid accidentally including sensitive or unintended files.
Handle upstream presence or absence by pushing to the correct remote (origin) and setting upstream when needed.

Quick Start

commit-push the current changes by generating a high-quality commit message, staging relevant files, committing, and pushing to the appropriate remote

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 in one step?▼

You can automate a git commit and push by using a tool that analyzes repository changes, generates a conventional commit message, stages relevant files, commits, and pushes to the remote in one sequence. This handles edge cases like missing upstreams safely.

What is a conventional commit message and how is it generated?▼

A conventional commit message follows a structured format reflecting the intent and scope of changes to improve history readability. It is generated automatically by analyzing the git state, including status, diff, and branch context.

Can I safely stage and push changes without including sensitive files?▼

Yes, you can safely stage and push changes without including sensitive files. The automation process uses guided prompts to validate diffs and helps you avoid accidentally committing sensitive or unintended files.

Does automated git push work if the branch has no upstream set?▼

Automated git push works even if the branch has no upstream set. The workflow detects upstream presence or absence and handles it by pushing to the correct remote and setting the upstream when needed.

What happens when committing code changes with no actual differences?▼

When committing code changes with no actual differences, the process detects the empty state as an edge case. It analyzes the git status and diff to determine if changes need to be committed before proceeding with the push.

What is the best way to handle uncommitted changes across multiple branches?▼

The best way to handle uncommitted changes across branches is to analyze the git state across the repository to determine what needs committing. This approach applies to repositories with uncommitted changes and guides staging safely.