skills.rest
DieStok
DieStokCOMMUNITY
Explore all skills by this author →
GitHub

ce-commit

Create conventional git commit messages from working tree changes.

Updated Apr 26, 2026
Search Tags:#git#commit#branching#developer-tools#version-control#conventional-commits
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-commit-diestok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-commit
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-commit
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-commit-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git commit messages are often vague or inconsistent. This skill guides you to craft a clear, value-driven commit message from your working tree changes, aligning with repo conventions.

Core Features & Use Cases

  • Conventional-commit-friendly: ensures messages follow conventional formats when possible, or a repo-specific convention if present.
  • Context-aware commits: analyzes git status, diff, branch, and recent commits to craft accurate messages.
  • Flexible workflow: handles staged and unstaged changes and can create feature branches when needed.

Quick Start

Ask the AI to create a well-formed commit for your current changes with a concise subject and optional body.

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 git working tree changes?▼

To generate conventional commit messages from git changes, analyze your working tree status, staged and unstaged diffs, and branch context to format a deterministic, value-driven message. This ensures consistency even when no specific repo convention is present.

What is the best way to write context-aware git commits for staged and unstaged changes?▼

Writing context-aware git commits involves gathering your current working tree diffs and recent commit history to construct an accurate message. This approach handles both staged and unstaged files safely while aligning with existing repository conventions.

Can I create a feature branch and commit my current working tree changes at the same time?▼

Yes, you can create a feature branch and commit your working tree changes together. The workflow supports optional branch naming alongside context-aware message generation, allowing you to safely stage and commit changes on a new branch.

Does this git commit tool work with repo-specific conventions or only standard conventional commits?▼

This git commit tool works with both standard conventional commits and repo-specific conventions. It analyzes your recent commit history to detect and align with existing repository formatting rules, defaulting to conventional formats only when no specific convention is found.

Why are my git commit messages vague and how do I format them consistently?▼

Git commit messages are often vague due to manual formatting inconsistencies. You can format them consistently by analyzing working tree diffs and recent history to automatically generate structured, conventional commit messages with a concise subject and optional body.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
Was85Was85

get-branch-name

Generate standardized Git branch names from a project PRD.

Community
Basic
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate