Skills Guide

Git Commit with Conventional Message

VerifiedSafe

Commits changes to git with a descriptive conventional commit message following standard conventions. Keeps commit history organized and clear.

Sby Skills Guide Bot
DevelopmentBeginner
306/2/2026
Claude Code
#git#conventional-commits#version-control

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Automates git commits with a conventional commit message after reviewing changes.

Strengths

  • Ensures consistent commit message format (conventional commits).
  • Automates staging all changes.
  • Provides a clear workflow from status to commit.

Limitations

  • Assumes all changes should be staged (may not be desired for partial commits).
  • Requires a predefined commit type; may not capture all nuances.
  • No interactive editing of commit message.
When to use it

Use when you have a set of changes ready to commit and want a standardized commit message.

When not to use it

Do not use when you need to selectively stage files or write a complex commit message manually.

Security analysis

Safe
Quality score80/100

The skill uses only git commands (status, diff, add, commit) with no network or destructive actions. The operations are legitimate for a version control workflow, and the Bash tool is restricted to git commands only.

No concerns found

Examples

Commit all changes
Commit all staged changes with a conventional commit message.
Commit with a specific message
Commit with message 'fix: resolve login bug'.

name: git-cm description: Commit changes to git with a descriptive conventional commit message. Use when ready to commit staged or unstaged changes. argument-hint: "[optional commit message]" disable-model-invocation: true allowed-tools: Bash(git:*)

Git Commit

Commit changes with a conventional commit message.

  1. Check the current git status to understand what has changed.

    • Command: git status

  2. View the diff if necessary to understand the changes better.

    • Command: git diff --staged or git diff

  3. Add all changes to the staging area (unless specific files are requested).

    • Command: git add .

  4. Commit the changes with a descriptive and conventional commit message.

    • Command: git commit -m "<type>: <subject>"
    • Ensure the message follows conventional commit standards (e.g., feat, fix, chore, docs, refactor).
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin