commit

Generate conventional Git commit messages and push to the remote repository.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the Git workflow by generating conventional commit messages and pushing changes, reducing manual messaging overhead and mistakes.

Core Features & Use Cases

  • Conventional messaging: Generate messages following the "type(scope): description" pattern for each commit.
  • Auto-stage & push: Auto-stages when nothing is staged and pushes after committing.
  • Use Case: When making frequent small changes, run this skill to produce consistent commit messages and keep remote branches up to date.

Quick Start

Use the commit skill to generate a conventional message for your current changes 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 generate conventional commit messages and push automatically?

To generate conventional commit messages and push automatically, use this skill to analyze unstaged or staged changes, auto-stage if needed, create messages following the type(scope): description pattern, and push to the remote repository.

What is a conventional commit message format for git?

A conventional commit message format follows the type(scope): description pattern. This skill enforces conventional commit types and supports an optional scope to produce clean, concise, and consistent messaging for your git workflow.

Can I auto-stage unstaged changes before committing to a remote branch?

Yes, you can auto-stage unstaged changes before committing. When nothing is staged in your local repository, this skill automatically stages your changes, generates a conventional commit message, commits, and pushes to the remote.

Does this git commit workflow handle multiple commits on various branches?

Yes, this git commit workflow handles multiple commits on various local branches. It targets typical development workflows by generating appropriate conventional commit messages for each commit and pushing the updates to the remote repository.

When should I not use an automated git commit and push approach?

You should not use an automated git commit and push approach when you need manual control over staging specific files or writing custom commit messages, as this skill always pushes after committing and auto-stages when nothing is staged.