ce-commit

Create git commits with conventional commit messages from repository context.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-commit-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-commit
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-commit
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-commit-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create well-structured git commits with clear, value-communicating messages, streamlining the process of saving changes to a repository.

Core Features & Use Cases

  • Commit Creation: Generates a single, well-crafted git commit from the current working tree changes.
  • Contextual Information: Provides context on git status, working tree diff, current branch, recent commits, and remote default branch.
  • Commit Message Convention: Determines commit message conventions based on project instructions, recent commit history, or defaults to conventional commit format.
  • Logical Commits: Splits changes into logical commits when necessary, ensuring a clear and organized commit history.
  • Staging and Committing: Stages and commits changes, ensuring that sensitive files and unrelated changes are not included.

Quick Start

Run the 'commit' command to create a git commit with a clear message.

Frequently Asked Questions about ce-commit

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

FAQPage Schema
How do I automate creating a git commit with a clear message?

To automate creating a git commit with a clear message, this Skill analyzes your working tree diff, recent log, and branch context to generate and stage a well-structured commit message automatically.

What is the conventional commit format and how is it applied here?

The conventional commit format is a standardized structure for commit messages. This Skill defaults to this format when no project-specific instructions are found in your recent commit history.

Can I split changes into logical commits within a single git repository?

Yes, you can split changes into logical commits within a git repository. The Skill evaluates your working tree diff and organizes unrelated changes into separate, logical commits for a clear history.

Does the commit message generation follow my existing project conventions?

Yes, the commit message generation follows your existing project conventions. It determines the appropriate style by checking project instructions and analyzing recent commit history before defaulting to conventional format.

How are sensitive files handled during the git staging and commit process?

During the git staging and commit process, sensitive files are securely excluded. The Skill ensures that unrelated changes and sensitive files are not included when staging and committing your working tree.