commit

Automate Git commits and pushes with conventional commit messages.

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/flosrn/.claude --skill commit-flosrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/flosrn/.claude/tree/main/skills/git-commit
Command: npx skills add https://github.com/flosrn/.claude --skill commit-flosrn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of committing code changes with standardized messages and automatically pushing them to the remote repository.

Core Features & Use Cases

  • Automated Git Commits: Generates conventional commit messages based on code changes.
  • Effortless Pushing: Pushes committed changes to the remote repository without user intervention.
  • Use Case: Quickly commit a set of related bug fixes with a fix(bug-id): description message and push them to the main branch.

Quick Start

Commit all staged changes with a conventional message and push to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit and push with conventional commit messages?

You can automate git commit and push by using a tool that generates conventional commit messages based on code changes and pushes them to the remote repository without manual intervention. This requires the Git CLI to manage version control operations.

What are conventional commits and when do I need them for version control?

Conventional commits are a standardized message structure for version control, such as fix(bug-id): description. You need them in software development workflows requiring frequent and standardized code updates to maintain clear project history.

Do I need Git CLI installed to automate committing and pushing code changes?

Yes, you need Git CLI installed to automate committing and pushing code changes. The process requires Git CLI to manage version control operations and enforce the conventional commit message structure locally.

What is the best way to quickly commit bug fixes and push to a remote branch?

The best way to quickly commit bug fixes and push to a remote branch is using an automated workflow that applies a conventional message like fix(bug-id): description and pushes the committed changes to the remote repository automatically.

Can I automatically generate commit messages based on my staged code changes?

Yes, you can automatically generate commit messages based on staged code changes. The automation analyzes your updates and applies a conventional commit message structure before pushing the changes to the remote repository.

Why does my automated git push fail when committing standardized messages?

Automated git push failures during standardized message commits often occur if the Git CLI environment is not properly configured or if remote repository permissions are missing. The process strictly requires Git CLI to manage version control operations.