commit

Generates conventional git commit messages with type, scope, and style rules.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/AdemKao/ai-cowork --skill commit-ademkao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AdemKao/ai-cowork/tree/main/.ai/skills/commit
Command: npx skills add https://github.com/AdemKao/ai-cowork --skill commit-ademkao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create well-formatted git commits following conventional commit standards. Use when committing changes, writing commit messages, or asked to commit code.

Core Features & Use Cases

  • Check current status and review changes before committing
  • Stage only related files to avoid mixing unrelated edits
  • Determine commit type and optional scope to produce consistent messages
  • Write clear, conventional commit messages following the defined rules
  • Provide examples and templates to accelerate team workflows

Quick Start

Generate a conventional commit message for the current changes following the commit type, scope, and style rules.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for my git changes?

To write a conventional commit message, you need to determine the commit type, optional scope, and formatted description based on your staged code changes. This ensures consistent git workflow messages across any project.

What are the conventional commit types and when should I use them?

Conventional commit types categorize the nature of your code changes for clearer project history and code review. The Skill guides you in selecting the correct type and documents examples for each to maintain consistent formatting rules.

How do I avoid mixing unrelated edits when preparing a git commit?

To avoid mixing unrelated edits, you should review your current status and stage only related files before committing. This keeps your conventional commit messages focused and accurately descriptive of the specific changes.

Can I use this to suggest a commit scope for my code changes?

Yes, the Skill suggests optional scopes for your conventional commit messages based on the reviewed code changes. This helps enforce formatting rules and produces consistent, well-formed git commit messages.

Does this conventional commit workflow require any specific git tools or dependencies?

No specific git tools or dependencies are required to format conventional commit messages. The Skill applies to code changes across any project by guiding developers through type, scope, and message formatting rules.