commit
Create a git commit for staged and unstaged changes in this repository. Use when the user asks to commit the current work, prepare a commit message, or stage and commit changes. Review git status and diffs, follow recent commit message style, avoid staging secrets such as .env files, create a concise conventional commit message, make the commit, and verify the result.
Best use case
commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a git commit for staged and unstaged changes in this repository. Use when the user asks to commit the current work, prepare a commit message, or stage and commit changes. Review git status and diffs, follow recent commit message style, avoid staging secrets such as .env files, create a concise conventional commit message, make the commit, and verify the result.
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?
Create a git commit for staged and unstaged changes in this repository. Use when the user asks to commit the current work, prepare a commit message, or stage and commit changes. Review git status and diffs, follow recent commit message style, avoid staging secrets such as .env files, create a concise conventional commit message, make the commit, and verify the result.
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
Create a git commit for the current repository changes. 1. Run `git status` to inspect changed and untracked files. 2. Run `git diff` and `git diff --staged` to inspect unstaged and staged changes. 3. Run `git log --oneline -5` to match recent commit message style. 4. Draft a concise conventional commit message such as `feat: ...`, `fix: ...`, `refactor: ...`, `chore: ...`, or `docs: ...`. 5. Stage only the relevant files. Do not stage secrets, credential files, or unrelated changes. 6. Create the commit with the drafted message. 7. Run `git status` again to confirm the commit succeeded.