commit

Analyze git changes to generate conventional single-line commit messages.

1.2k|100|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/clacky-ai/openclacky --skill commit-clacky-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/clacky-ai/openclacky/tree/main/.clacky/skills/commit
Command: npx skills add https://github.com/clacky-ai/openclacky --skill commit-clacky-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes git changes to generate concise, semantic, single-line commit messages.

Core Features & Use Cases

  • Analyze staged and unstaged changes across multiple files to determine a cohesive story
  • Generate conventional commit messages (feat, fix, chore) that reflect the primary purpose of the changes
  • Enforce single-line messages and provide guidance on grouping related changes for a clean history
  • Integrate into your workflow to prepare commits before saving or pushing

Quick Start

Invoke the skill with a command like: commit my changes using semantic, single-line messages.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for multiple file changes?

To generate conventional commit messages, analyze staged and unstaged changes across multiple files to determine a cohesive story, then produce a single-line message reflecting the primary purpose of those changes.

What is a semantic single-line git commit and when do I need it?

A semantic single-line git commit is a concise message following conventional commit rules that groups related changes into one cohesive narrative, needed when you want a clean, feature-focused version-control history.

Can I group unrelated git changes into a single conventional commit?

You can group related git changes into a single conventional commit by analyzing the overall narrative, though generating a cohesive message works best when the staged and unstaged files share a primary purpose.

Does this approach support both staged and unstaged git changes for commit generation?

Yes, semantic commit message generation analyzes both staged and unstaged git changes across multiple files to determine the cohesive story before enforcing a single-line conventional message.

What's the best way to automate conventional commit message creation for clean version control?

The best way to automate conventional commit creation is to analyze git changes, determine the primary feature purpose, and enforce a single-line semantic message that integrates directly into your workflow before pushing.