Commit
Create git commits that follow Conventional Commits conventions, enabling automatic changelog and release note generation. The skill stages your changes, validates them through pre-commit hooks, and ensures commit messages match your project's standards before recording them to history.
Commit stages and records your code changes with Conventional Commits messages that auto-generate changelogs.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
Commit stages and records your code changes with Conventional Commits messages that auto-generate changelogs. Create git commits that follow Conventional Commits conventions, enabling automatic changelog and release note generation. The skill stages your changes, validates them through pre-commit hooks, and ensures commit messages match your project's standards before recording them to history.
Use it when
- Commit captures staged changes and records them to your repository history with a message explaining what changed and why.
- Commit enforces Conventional Commits conventions for your messages, which standardize how you describe changes.
Install
kdlbs/kandev/commit · repository language: Go
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I commit code changes to my repository?
Commit lets you save and record code changes with a commit message to version control. Stage your modified files, then Commit creates a snapshot of those changes with a descriptive message following Conventional Commits conventions. This records your work to the project history and enables automatic changelog generation.
What does Commit do in the version control workflow?
Commit captures staged changes and records them to your repository history with a message explaining what changed and why. Commit validates your changes through pre-commit hooks and ensures your commit message matches your project's standards before finalizing the save, helping maintain clean project history.
How should I write a commit message following best practices?
Commit enforces Conventional Commits conventions for your messages, which standardize how you describe changes. This structure enables Commit to automatically generate changelogs and release notes from your commit history, making your project's evolution transparent and your messages consistently clear.
What happens when I execute a commit operation on staged files?
Commit takes your staged files and creates a permanent snapshot in your repository history with your provided message. Commit runs pre-commit validation hooks to catch issues before recording, ensuring only quality changes are saved and your commit message adheres to project standards.
Can Commit help track my project's history through commits?
Yes, Commit records each change you make with a descriptive message, building a complete timeline of your project's evolution. By following Conventional Commits conventions, Commit enables you to generate automatic changelogs and release notes directly from your commit history, making it easy to understand what changed and when.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Save and record code changes with a commit message”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Configure pre-commit, commit-msg, and pre-push hooks to standardize your team's development workflow. Supports both husky and native git hooks, with built-in linting, code formatting, commit message validation, and secret detection to catch issues before they reach your repository.
Adapt Conventional Commits for Chinese development teams with localized type definitions, message templates, and tooling integration. Configure commitlint, husky, and conventional-changelog to enforce consistent commit practices across your team while keeping type keywords in English for tool compatibility.
Git Hygiene Enforcer helps teams standardize development practices by automating commit validation, branch naming enforcement, and pull request workflows. It provides ready-to-use configurations for commit hooks, branch protection rules, and CI/CD checks that maintain code quality without manual oversight.
Create Commit analyzes your staged changes and generates properly formatted conventional commits, automatically inferring commit type and scope from the diff. It detects breaking changes and flags potential secrets before committing, while enforcing pre-commit hooks to maintain code quality standards.
Commit stages files based on scope, intent, or both—parsing file paths, folders, and free-text descriptions to guide commit messages. Supports amending the last commit and integrates with sequenced workflows where the caller owns the final commit step.
Commit automates version control by enforcing atomic commits—one logical change per commit—with built-in safeguards against committing to main/master branches. It guides you through branch creation, staged change review, and properly formatted commit messages to keep project history clear and reversions safe.
More skills commit (MIT) · Cp (unlicensed) · Woocommerce Git Commit (unlicensed)