Automatically stage changes and generate conventional commit messages for your current git worktree.
Install
mkdir -p .claude/skills/commit-changes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17081" && unzip -o skill.zip -d .claude/skills/commit-changes && rm skill.zipInstalls to .claude/skills/commit-changes
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.
Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.Key capabilities
- →Gather context from user notes and git status
- →Review changed files in the working tree
- →Stage relevant files for commit
- →Use imperative mood for commit messages
- →Incorporate user-provided context into messages
How it works
This skill creates a focused git commit by first gathering context from the working tree and user notes, then staging relevant files while avoiding sensitive data, and finally generating a conventional commit message following specified guidelines.
Inputs & outputs
When to use commit-changes
- →Generate commit messages for changes
- →Stage files for commit
- →Maintain project commit history
About this skill
Commit changes
Create a focused git commit for the current changes.
Workflow
- Gather context:
- User notes, if provided.
- Current branch:
git branch --show-current. - Working tree:
git status --short. - Staged changes:
git diff --cached --stat. - Unstaged changes:
git diff --stat. - Recent commits for style reference:
git log -5 --oneline.
- Review the changed files.
- If there are no changes to commit, tell the user and stop.
- If there are unstaged changes, stage the relevant files with
git add. - Do not stage files that look like secrets, credentials, API keys, or private environment files.
- Write a conventional commit message:
type(scope): brief description
Optional longer explanation if the changes are complex.
Allowed types: feat, fix, refactor, test, docs, chore, perf, style, build, ci.
Message guidelines
- Keep the first line under 72 characters.
- Use imperative mood, for example
add feature, notadded feature. - Be specific about what changed and why.
- Incorporate user-provided context when it clarifies intent.
Commit rules
- Use
git commit -m "message". - Do not push.
- Do not amend unless explicitly requested.
- Do not use
--no-verify. - Do not include AI attribution.
If the commit fails because of hooks, fix mechanical formatting, lint, or import issues and retry. If the hook failure reveals a meaningful product or implementation issue, stop and ask the user how to proceed.
When not to use it
- →When committing sensitive data like secrets or credentials
- →When amending commits without explicit request
Limitations
- →The skill does not amend commits unless explicitly requested.
- →The skill does not use `--no-verify`.
How it compares
This workflow automates the creation of conventional git commits by systematically reviewing changes, staging files, and generating messages based on established guidelines, ensuring consistency and clarity in commit history compared to man
Compared to similar skills
commit-changes side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit-changes (this skill) | 0 | 3mo | No flags | Beginner |
| run-nx-generator | 5 | 3mo | Review | Intermediate |
| git-commit | 11 | 7mo | Review | Beginner |
| morph-search | 9 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by tldraw
View all by tldraw →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対応を依頼された時に使用。