ce-commit

Generate conventional git commit messages from working tree changes.

10|Updated Dec 13, 2016

Search Tags:#automation #git #workflow #commit #code-quality #version-control #conventional-commits

Ready to run

npx skills add https://github.com/vitallium/dotfiles --skill ce-commit-vitallium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-commit
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-commit
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-commit-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a single, clear git commit message that communicates why changes were made, aligning with repo conventions when present.

Core Features & Use Cases

Generates well-structured commits that follow conventional commits by default and adapt to project-specific conventions when available.
Analyzes the working tree to propose an appropriate subject, scope, and optional body to explain the motivation behind changes.
Supports automatic branch creation when committing to default branches or when the workflow requires a feature branch.

Quick Start

When you are ready to save changes, ask to create a concise, value-focused commit message and apply it to the current changes.

Frequently Asked Questions about ce-commit

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

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

Generating conventional commit messages from staged changes involves analyzing the working tree to propose a subject and optional body. The tool detects repository conventions from recent history to ensure consistent formatting.

What is the best way to automate consistent git commit formatting across a project?▼

Automating consistent git commit formatting involves analyzing recent project history to infer patterns and applying conventional commit standards. This approach adapts to project-specific conventions when available, ensuring aligned messaging.

Do I need to manually stage files before creating a conventional commit message?▼

You need changes in your working tree to create a commit message. The process analyzes current changes to propose a properly formatted subject and optional body for staging commits using a heredoc message.

Can I automatically create a feature branch when committing to the default branch?▼

Yes, you can automatically create a feature branch when committing to default branches. The workflow supports automatic branch creation when the development process requires a feature branch.

How does the tool detect existing repository conventions for version control commits?▼

To detect existing repository conventions for version control commits, the tool analyzes recent commit history to infer patterns. It then uses these patterns to adapt its output to project-specific messaging styles.