ce-commit

Generate git commit messages from status, diff, branch, and log data.

14|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-commit-ouro-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-commit
Source: https://github.com/Ouro-labs/ouroboros-plugins/tree/main/plugins/compound-engineering/assets/skills/ce-commit
Command: npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-commit-ouro-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating clear, value-communicating git commits, reducing the effort required to follow repository conventions.

Core Features & Use Cases

  • Structured Commit Messages: Generates well-structured commit messages that adhere to repository conventions.
  • Contextual Data Utilization: Utilizes git status, working tree diff, branch, recent commits, and remote default branch for informed commits.
  • Branch Management: Handles detached HEAD states and prompts for feature branch creation if necessary.
  • Commit Convention Adaptation: Follows repository-specific conventions, recent commit history, or defaults to conventional commit format.

Quick Start

To create a commit with this skill, simply provide the "commit" command.

Frequently Asked Questions about ce-commit

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

FAQPage Schema
How do I generate structured git commit messages automatically?

You can generate structured git commit messages by running the "commit" command, which analyzes your working tree diff, branch context, and recent history to produce clear, convention-compliant messages automatically.

How do I commit code following conventional commit format?

To commit code following conventional commit format, this Skill adapts to your repository's specific conventions by checking recent commit logs, defaulting to standard conventional commit structures if no custom repository rules are detected.

How does this tool handle git commits in a detached HEAD state?

When handling git commits in a detached HEAD state, the Skill detects the context using git branch data and prompts you to create a feature branch before committing, ensuring changes are safely saved to a valid reference.

Do I need to configure anything before using this Skill to structure my git commits?

You do not need to configure anything before using this Skill to structure your git commits, as it operates directly within git repositories and requires no external dependencies to analyze diffs and generate messages.

What is the best way to write value-communicating git commit messages?

The best way to write value-communicating git commit messages is to utilize contextual data like working tree diffs and remote default branch information, which this Skill uses to ensure your commits clearly explain the value of the changes.