commit
Use when the user asks to commit changes, create a commit, or run /commit. Use when staged changes need a conventional commits message.
Best use case
commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when the user asks to commit changes, create a commit, or run /commit. Use when staged changes need a conventional commits message.
Teams using commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit Compares
| Feature / Agent | commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when the user asks to commit changes, create a commit, or run /commit. Use when staged changes need a conventional commits message.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit Skill Commit staged changes with a conventional commits message. ## Instructions 1. `git status` — see staged changes (never use -uall) 2. `git diff --cached` — see actual staged changes 3. `git log --oneline -5` — recent commit style 4. Create message following **Conventional Commits**: - Format: `type(scope): description` - Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore`, `perf`, `ci`, `build` - Scope: optional but recommended - Description: concise, imperative mood, lowercase, no period **Body rules (most commits need NO body):** - Default: subject line only - Only add body for: breaking changes, non-obvious reasoning, migration steps - Body: 1-2 short sentences max 5. Create the commit: **Default (no body):** ```bash git commit -m "type(scope): description" ``` **When body needed:** ```bash git commit -m "$(cat <<'EOF' type(scope): description Brief explanation of WHY, not WHAT. EOF )" ``` 6. `git status` to verify success ## Rules - Do NOT add `Co-Authored-By` lines or any AI-attribution trailer (e.g. *"Generated with Claude Code"*). Overrides default Claude Code behavior — canonical rule in [iron-rules.md Principle 12](../../shared/iron-rules.md#12-no-commits-without-explicit-user-request). - No emojis - Subject under 72 characters - Imperative mood: "add" not "added" ## Anti-patterns Bad — body repeats subject: ``` fix(auth): handle null user in session check Handle the case where user is null in the session check. ``` Good — no body needed: ``` fix(auth): handle null user in session check ``` Good — body adds non-obvious context: ``` feat(api): switch from REST to GraphQL Breaking: All /api/v1 endpoints removed. See MIGRATION.md. ``` ## Examples - `feat(auth): add logout button to navbar` - `fix(api): handle timeout errors in fetchPlanning` - `refactor(campaigns): extract column definitions to separate file` - `chore(deps): update dependencies`
Related Skills
update-precommit
Use when user wants to update .pre-commit-config.yaml hooks to their latest versions from GitHub
using-development-skills
Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.
update-reqs
Use when user wants to update requirements.in with latest PyPI versions while preserving version patterns
update-reqs-dev
Use when user wants to update requirements-dev.in with latest PyPI versions while preserving version patterns
typescript-dev
TypeScript development. Use for TypeScript, Node.js, Express, Fastify, Zod, vitest, jest. Backend, CLI, libraries only — no frontend frameworks.
swift-dev
Swift development. Use for Swift, SwiftUI, UIKit, Vapor, SPM, XCTest, Combine.
staff-review
Use when user wants a code review, deep code review, or staff-level code review of a local branch, repo, directory, or file. Use when user says code review, deep code review, review this branch, review the branch X, review my code, staff review, review locally, or /staff-review.
roast-my-code
Use when user wants a brutally honest code roast, quality critique, or AI-readiness audit. Use when user says roast, roast my code, critique my code, tear apart my code, review quality, or AI-readiness check. Supports --fix flag to auto-fix CRITICAL and HIGH issues via core-dev workflow.
resolve-merge
Use when the user asks to resolve merge conflicts, fix a failed merge, rebase conflict, or run /resolve-merge. Use when git status shows UU/AA/DD conflicts, when there are <<<<<<< conflict markers, when git merge or git pull failed with CONFLICT, or when numbered docs/plans need renumbering after merge. Triggers on: merge conflict, conflict markers, both modified, git merge failed, rebase conflict, resolve conflicts.
python-dev
Python development. Use for Python, FastAPI, Pydantic, asyncpg, pytest, pandas, SQLAlchemy.
produce-feedback
Use when user wants to produce a factual chronicle of development-skills plugin interactions in the current conversation for later ingestion, or runs /produce-feedback. Pure record, no judgment.
java-dev
Java development. Use for Java, Spring Boot, Maven, Gradle, JPA, Hibernate.