skills.rest
wollfoo
wollfooCOMMUNITY
Explore all skills by this author →
GitHub

commit-push

Stage all changes, commit with conventional prefixes, and push to a remote branch.

Updated Nov 20, 2025
Search Tags:#git#version control#commit#conventional commits#push#code deployment
One-click install
npx skills add https://github.com/wollfoo/codex-cli --skill commit-push-wollfoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/wollfoo/codex-cli/tree/main/skills/commit-push
Command: npx skills add https://github.com/wollfoo/codex-cli --skill commit-push-wollfoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of committing and pushing code changes to a Git repository, ensuring consistency and adherence to conventional commit message standards.

Core Features & Use Cases

  • Automated Staging: Stages all current changes in the repository.
  • Conventional Commits: Helps generate commit messages following established prefixes like feat:, fix:, docs:, etc.
  • Push to Remote: Pushes committed changes to the specified remote branch (defaults to origin main).
  • Use Case: After completing a new feature, you can use this Skill to quickly stage, commit with a descriptive message (e.g., feat: implement user authentication), and push your changes to the main branch.

Quick Start

Use the commit-push skill to add all changes, commit them with the message "feat: update documentation", and push 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 operations with conventional commit messages?▼

Automating git commit and push requires staging all current changes, generating a message with predefined prefixes like feat: or fix:, and pushing to a remote repository branch such as origin main.

What are conventional commits and how do they organize git history?▼

Conventional commits use established prefixes like feat:, fix:, and docs: to categorize code changes, ensuring a clean and organized git history across software development workflows.

How do I stage all changes and push code to a remote repository?▼

To stage and push code, the process adds all current repository changes, commits them with a descriptive conventional message, and pushes those committed changes to the specified remote branch.

Can I push committed changes to a specific remote branch other than the default?▼

Pushing committed changes defaults to the origin main remote repository branch, maintaining consistency in code deployment while supporting standard git version control workflows.

Does this git automation tool require any dependencies or components?▼

This git automation tool requires no external dependencies or components, functioning independently to stage changes, generate conventional commit messages, and push to remote repositories.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
nashgaonashgao
3

Git Push, Pull & Fetch Operations

Manage Git push, pull, and fetch operations with safety checks.

Community
Advanced
massgenmassgen
1.1k

pr-checks

Automate PR checks with pre-commit hooks, tests, and CodeRabbit feedback.

Official
Advanced
mhattingpetemhattingpete
657

git-pushing

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

Community
Basic