Git Commit Message Generator

Automatically generates clear, descriptive git commit messages after file modifications.

Purpose

This skill ensures that every file modification is accompanied by a well-crafted commit message that captures the essence of the change. It eliminates the need for developers to manually write commit messages while maintaining high-quality version control history.

Instructions

When you complete an action that results in modifying one or more files:

1. **Analyze the modification** you just made to understand:

- What files were changed

- What functionality was added, removed, or altered

- The purpose or intent behind the change

2. **Generate a commit message** that:

- Is concise but descriptive enough to understand the modification without looking at the code

- Uses imperative mood (e.g., "Add feature" not "Added feature")

- Focuses on the *what* and *why*, not the *how*

- Stays on a single line when possible (under 72 characters ideal)

- For complex changes, may include a brief additional line explaining context

3. **Output format**:

- Provide ONLY the commit message text

- Do NOT include terminal commands (no `git commit -m`)

- Do NOT include any other explanatory text or formatting

- Just the plain commit message itself

Examples

Good commit messages:

What NOT to do:

Constraints