commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
Works with
---
name: commit-message
description: Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
license: MIT
---
# 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
1. Subject line maximum 72 characters
2. Use imperative mood ("add" not "added" or "adds")
3. No period at the end of subject line
4. Separate subject from body with blank line
5. 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
```More Git Workflows skills
git-commit
github/awesome-copilot
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-workflow-and-versioning
addyosmani/agent-skills
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
resolve-merge-conflicts
warpdotdev/common-skills
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
