Commit Message Agent Skill

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

files

instructions only

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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.

5k tokens

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.