commit

Write structured git commit messages with imperative first lines and issue references.

1|Updated Mar 7, 2026

Search Tags:#git #code review #version control #commit #message crafting

Ready to run

npx skills add https://github.com/cosmoscalibur/agent-hardness --skill commit-cosmoscalibur

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cosmoscalibur/agent-hardness/tree/main/skills/commit
Command: npx skills add https://github.com/cosmoscalibur/agent-hardness --skill commit-cosmoscalibur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that commit messages are clear, concise, and adhere to best practices, making code reviews and history more readable.

Core Features & Use Cases

Imperative First Line: Promotes a clear and actionable commit message.
Body Optimization: Helps create body text that adds context without redundancy.
Issue References: Encourages referencing related issues/PRs for clarity.
One-File-One-Commit: Enforces a single commit per file for better history organization.
Human Authorship: Ensures that commit authorship is not attributed to AI agents.

Quick Start

Generate a commit message for the changes made in 'feature/new-feature.md'.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write a clear git commit message for code review?▼

Write clear git commit messages by using an imperative first line, adding an optional body for non-obvious changes, and referencing related issues or PRs to improve readability. This makes code reviews and history easier to follow.

What is the one-file-one-commit rule in version control?▼

The one-file-one-commit rule in version control enforces creating a single commit per file. This practice ensures better history organization and makes tracking specific changes during code review much easier.

How do I structure a git commit body without being redundant?▼

Structure a git commit body by using git diff to describe changes and adding context only for non-obvious modifications. This optimization prevents redundancy while ensuring the commit history remains clear and concise.

Why does proper commit message crafting require human authorship?▼

Proper commit message crafting requires human authorship to ensure that version control accountability is correctly attributed to the developer rather than AI agents. This maintains accurate and transparent git history.

Can I use imperative mood for the first line of a commit message?▼

Yes, you can use imperative mood for the first line of a commit message. This approach promotes a clear and actionable statement of what the patch does, adhering to standard version control best practices.