commit Skill
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'. Published by microsoft in vscode.
What is commit Skill?
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode
Technical details
- Install or run with Copy skill directory
When to use commit Skill
- Use it for developers using vscode.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: src/vs/sessions/skills/commit/SKILL.md
What it does
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
Skill instructions
<!-- 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 to sample recent commits and the user's own commits: Recent repo commits (for overall style) git log --oneline -Explore related resources
Frequently asked questions
What is commit?
commit is a open-source AI agent skill with Copy skill directory. Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style.
Who is commit best for?
commit is best for reusing agent instructions, scripts, and references.
How do I install commit?
Install or run commit using Copy skill directory. Check commit for the latest setup command.
Is commit actively maintained?
commit may need a closer maintenance check before production use.
Auto-fetched from GitHub.
