commit
This skill analyzes your repository's commit history to detect its message style, then generates a subject line and optional body that fit the established pattern. It stages unstaged changes when needed, respects pre-commit hooks and signing requirements, and confirms the commit with a log preview.
Commit commits staged or unstaged code changes with an AI-generated message that matches your repository's existing style.
AI-generated summary based on this skill's SKILL.md
Install
microsoft/vscode/commit · repository language: TypeScript
git clone https://github.com/microsoft/vscode
cp -r vscode/src/vs/sessions/skills/commit ~/.claude/skills/commitnpx skillfed install microsoft/vscode/commitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I commit my changes with an AI-generated message?
commit analyzes your repository's commit history to detect its message style, then generates a subject line and optional body that fit the established pattern. The skill stages unstaged changes when needed, respects pre-commit hooks and signing requirements, and confirms the commit with a log preview before finalizing.
Can commit stage and commit unstaged changes?
Yes. commit can stage unstaged changes as part of the workflow. It handles both staged and unstaged modifications, ensuring all your work is captured in a properly formatted commit that follows your repository's conventions.
Does commit generate messages following repository conventions?
commit generates commit messages by analyzing your repository's existing commit history to detect its style pattern. It then creates a subject line and optional body that match the established conventions—whether that's conventional commits, a custom format, or another standard your repo uses.
What safety features does commit include?
commit respects pre-commit hooks and signing requirements to ensure safe, compliant commits. It confirms the commit with a log preview before finalizing, so you can verify the message and changes match your expectations before they're saved to git.
How does commit save my code changes?
commit creates a properly formatted commit by analyzing your repository's style, generating an appropriate message, staging any unstaged changes, and respecting your repo's hooks and signing setup. It then previews the commit log so you can confirm before the changes are saved to your repository.
SKILL.md
rendered from the published skill — quoted content, verbatim
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->
Commit Changes
Help the user commit code changes with a well-crafted commit message derived from the diff, following the conventions already established in the repository.
Guidelines
- Never amend existing commits without asking.
- Never force-push or push without explicit user approval.
- Never skip pre-commit hooks (do not use
--no-verify). - Never skip signing commits (do not use
--no-gpg-sign). - Never revert, reset, or discard user changes unless the user explicitly asked for that.
- Check for obvious secrets or generated artifacts that should not be committed. If something looks risky - ask the user.
- When in doubt about staging, convention, or message content — ask the user.
Workflow
1. Discover the repository's commit convention
Run the following
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
src/vs/sessions/skills/commit/SKILL.md