commit-workflow

Standardized commit messages follow a conventional format with a type prefix (feat, fix, refactor, docs, style, test, build) followed by a brief description. This Skill automates the process by analyzing your staged changes and generating commits that enforce this structure, ensuring consistency across your project history.

Commit only staged changes by using git diff --cached to review what you've staged, then create your commit from that snapshot alone. This Skill focuses exclusively on staged files, ignoring unstaged modifications, so your commits capture exactly what you've prepared.

Yes. This Skill automates commit creation for staged changes through a /commit-staged command, generating standardized messages and updating your repository history. You can also follow manual steps to craft meaningful commits that meet your project's conventions.

Documentation updates are part of the commit workflow—this Skill enforces updating README or related docs when new features are added. By including documentation changes in your commit, you keep your project's documentation aligned with code changes.

Conventional commit messages are essential in team projects and codebases where clear history and automated tooling matter. They make it easy to generate changelogs, track feature additions, and understand why changes were made at a glance.

This Skill supports both workflows. You can use the automated /commit-staged approach to generate commits based on your staged changes, or follow manual steps to craft commits yourself while adhering to the standardized format and message structure.