ce-commit

Group repository changes into conventional git commits with subject lines.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-commit
Source: https://github.com/thisisryanswift/zellij-agent-tools/tree/main/.opencode/skills/ce-commit
Command: npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In many projects, commit messages are vague, inconsistent, or hard to trace, making history hard to interpret and review.

Core Features & Use Cases

  • Automatically derive concise subject lines from changes and group related files into logical commits.
  • Enforce or align with repository conventions, including conventional commits, across the project.
  • Use cases include feature development, bug fixes, and refactors with clear, purposeful messages.

Quick Start

Provide a single, well-structured commit message for the current changes, following conventional commit guidelines.

Frequently Asked Questions about ce-commit

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

FAQPage Schema
How do I automate conventional commit messages for my git workflow?

You can automate conventional commit messages by analyzing raw repository changes, deriving concise subject lines, grouping related files, and outputting structured git commits that align with repo conventions.

Can I group multiple file changes into a single logical commit automatically?

Yes, raw code changes are analyzed and grouped into logical commits based on recent commit style cues, ensuring that related files are bundled together with clear, purposeful messages.

Does this commit automation tool follow existing repository conventions?

The commit automation follows repo conventions when available, analyzing recent commits for style cues to enforce consistent conventional commit messages across the project and software team.

What is the best way to write conventional commits for feature development and bug fixes?

The best way to write conventional commits is to automatically derive a subject line with an optional body from repository changes, ensuring clear, purposeful messages for features, bug fixes, and refactors.

How does this tool format the subject line and body for conventional commits?

It formats conventional commits by outputting a concise subject line derived from raw changes, accompanied by an optional body, structured to follow conventional commit guidelines and recent repo style cues.