commit

What it does and when to use it

Create commits following repo conventions. Use when committing changes, creating commit messages.

How it works

1. Quick Start
2. Commit Message Format
3. Core Patterns
4. Execution Steps
5. References

---
name: commit
description: Create commits following repo conventions. Use when committing changes, creating commit messages.
allowed-tools: Bash, Read, Glob, Grep
---

# Git Commit Skill

## Quick Start

```bash
/commit  # Analyze changes and auto-commit
```

## Commit Message Format

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

## Core Patterns

### Type

| Type     | Purpose       |
| -------- | ------------- |
| feat     | New feature   |
| fix      | Bug fix       |
| chore    | Build, config |
| refactor | Refactoring   |
| docs     | Documentation |
| test     | Tests         |

### Scope

| Category | Example                                      |
| -------- | -------------------------------------------- |
| Item     | `useToggle`, `SwitchCase`, `mergeRefs`       |
| Area     | `docs`, `codemod`, `ci`, `plugin`            |
| None     | Omit scope when the change spans the package |

### Examples

```bash
feat(useDebounce): add a maxWait option
fix(useKeyboardHeight): ignore transient zero heights on Android
fix: correct SSR rendering logic
docs(useToggle): update the example
chore: add claude skills
```

## Execution Steps

1. `git status` - Check changed files
2. `git diff` - Analyze changes
3. Determine type, scope, and description
4. `git add .` + `git commit`

## References

- [details.md](references/details.md) - Full conventions and complex cases

Versions

Database snapshot: 13.11.2026 · package version b8942f71b970 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100conventional-commit
  Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
• 100conventional-commits
  Use when creating git commits, writing commit messages, or following version control workflows
• 100conventional-commits
  Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
• 100aif-commit
  Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
• 100commit-helper
  Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
• 100git-commit
  Guide for Git commit messages and pushing code. Use when user says "commit", "push code", "push to git", "save changes to git", "git add and commit", "commit and push", or needs help writing commit messages following Conventional Commits.