commit
Writes and creates conventional commits based on your current git changes.
Install
mkdir -p .claude/skills/commit-nethesis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19260" && unzip -o skill.zip -d .claude/skills/commit-nethesis && rm skill.zipInstalls to .claude/skills/commit-nethesis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review git changes, write a Conventional Commit message, and create a git commit without pushing. Use when the user wants to commit all current changes or a specific scoped subset of files.Key capabilities
- →Review current git changes using `git status --short`.
- →Inspect relevant diffs for a requested scope.
- →Stage specific files or hunks for a commit.
- →Write a Conventional Commit message following specified rules.
- →Create a git commit.
- →Report the final commit hash and subject.
How it works
The skill reviews the current working tree, stages intended files, and then creates a commit with a Conventional Commit message.
Inputs & outputs
When to use commit
- →Create a commit for all staged changes
- →Review and commit a subset of modified files
- →Generate a conventional commit message for a bug fix
About this skill
Commit
Use this skill when the task is to inspect the current git changes, prepare a Conventional Commit message, and create a commit.
Constraints
- Do not push, amend, rebase, or rewrite history unless the user explicitly asks.
- Do not include unrelated changes when the requested commit scope is narrower than the full working tree.
- Only create a commit after reviewing the current git status and the relevant diff.
- If the requested scope is ambiguous, clarify the intended files before staging or committing.
Procedure
- Review the current working tree with
git status --shortand inspect the relevant diff for the requested scope. - Decide whether the current changes belong in one coherent commit or should be split into multiple commits.
- If only part of the working tree should be committed, stage only the intended files or hunks.
- Write a Conventional Commit message that matches the actual change.
- Create the commit.
- Report the final commit hash and subject back to the user.
Commit Message Rules
- Use the format below.
- Keep the subject line at 50 characters or fewer.
- Use imperative mood.
- Capitalize the subject.
- Do not end the subject with a period.
- Add a body only when it improves clarity.
- When a body is needed, leave one blank line before it and wrap lines near 72 characters.
- Explain both what changed and why, not just the file list.
Commit Format
<type>(<scope>): <subject>
<body>
Valid type examples: feat, fix, docs, refactor, test, chore, ci, build, perf.
If no conventional scope is helpful, omit the parentheses and use <type>: <subject>.
Output Expectations
After committing, provide:
- The commit hash
- The final subject line
- A short summary of what was included in the commit
When not to use it
- →When the user explicitly asks to push changes.
- →When the user explicitly asks to amend, rebase, or rewrite history.
- →When the requested commit scope is narrower than the full working tree but unrelated changes are included.
Limitations
- →It does not push, amend, rebase, or rewrite history.
- →It only creates a commit after reviewing the current git status and relevant diff.
- →It requires clarification if the requested scope is ambiguous before staging or committing.
How it compares
This skill automates the review, staging, and commit message generation process, unlike manually performing each git command.
Compared to similar skills
commit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit (this skill) | 0 | 3mo | No flags | Beginner |
| run-nx-generator | 5 | 2mo | Review | Intermediate |
| git-commit | 11 | 6mo | Review | Beginner |
| morph-search | 9 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
git-commit
github
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
morph-search
parcadei
Fast codebase search via WarpGrep (20x faster than grep)
upgrading-expo
sickn33
Upgrade Expo SDK versions
continue-implementation
LibPDF-js
Continue implementing a spec from a previous session
fix-dependabot-prs
bannzai
dependabotから上がってきた複数のPRを一括で解決し、まとめPRを作成する。dependabotのPR対応を依頼された時に使用。