mcpbeat

Commit Message

github/commit-message

Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help

305 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2768
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/github/copilot-cli-for-beginners --skill commit-message

The instruction itself

5 sections, as written by the author

Commit Message Skill

Generate commit messages following the Conventional Commits specification.

Format

<type>(<scope>): <description>

[optional body]

[optional footer]

Types

| Type | When to Use |

|------|-------------|

| feat | New feature |

| fix | Bug fix |

| docs | Documentation only |

| style | Formatting (no code change) |

| refactor | Code change that neither fixes nor adds |

| perf | Performance improvement |

| test | Adding or updating tests |

| chore | Maintenance tasks |

Rules

  • Subject line maximum 72 characters
  • Use imperative mood ("add" not "added" or "adds")
  • No period at the end of subject line
  • Separate subject from body with blank line
  • Body explains what and why, not how

Examples

Simple:

fix(auth): prevent redirect loop on expired sessions

With body:

feat(api): add rate limiting to public endpoints

- Limits requests to 100/minute per IP
- Returns 429 status with retry-after header
- Configurable via RATE_LIMIT_MAX env variable

Closes #234

How to use it

Copy the folder

Take github/commit-message from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.