khaneliman / commit-messages
Install for your project team
Run this command in your project directory to install the skill for your entire team:
mkdir -p .claude/skills/commit-messages && curl -L -o skill.zip "https://fastmcp.me/Skills/Download/2911" && unzip -o skill.zip -d .claude/skills/commit-messages && rm skill.zipProject Skills
This skill will be saved in .claude/skills/commit-messages/ and checked into git. All team members will have access to it automatically.
Important: Please verify the skill by reviewing its instructions before using it.
Generate conventional commit messages based on staged changes. Use when writing commit messages, understanding conventional commit format, or ensuring consistent commit history.
0 views
0 installs
Skill Content
--- name: commit-messages description: Generate conventional commit messages based on staged changes. Use when writing commit messages, understanding conventional commit format, or ensuring consistent commit history. --- # Commit Message Guide Generates conventional commit messages that are clear, consistent, and informative. ## Core Principles 1. **Follow Project Style** - Mimic existing `git log` patterns above all else. 2. **Imperative mood** - "add feature" not "added feature" 3. **Explain why** - Body explains motivation, not just what changed 4. **Concise subject** - 72 characters or less, no period 5. **Scope when helpful** - Include scope when it clarifies the change ## Commit Formats ### 1. Conventional Commits (Standard) The most common standard, widely used across the industry. ``` <type>(<scope>): <subject> ``` _Example:_ `feat(auth): add login page` ### 2. Path-Based / Scoped (Alternative) Common in monorepos or systems like Nixpkgs. ``` <path/to/component>: <subject> ``` _Example:_ `programs/waybar: update config` ## Detailed Reference Material - [reference.md](reference.md) - **Commit Types** table, Scope determination, **Breaking Changes**, and **Alternative Conventions**. - [examples.md](examples.md) - Good and bad examples for various scenarios. ## Analyzing Changes for Commit Type 1. **Look at files changed** - New files = likely `feat` - Test files only = `test` - Config/build files = `build` or `ci` - README/docs = `docs` 2. **Examine the diff** - Bug fix patterns = `fix` - New exports/functions = `feat` - Restructuring = `refactor` - Optimizations = `perf` 3. **Check `git log`** - Verify if the repo uses `type(scope):` or `path/to/file:` style. ## See Also - **Code review**: See [code-review](../code-review/) for reviewing commits - **Git workflows**: See [git-workflows](../git-workflows/) for branching strategies