Skills Guide

Git Commit with Conventional Message

VerifiedSafe

Commits staged or unstaged changes with a descriptive conventional commit message following version control standards.

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

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Commits changes to a Git repository with a conventional commit message after reviewing and staging changes.

Strengths

  • Enforces conventional commit format (feat, fix, chore, etc.)
  • Reviews changes before committing
  • Stages all changes automatically
  • Generates descriptive messages following standards

Limitations

  • Only performs 'git add .' (no selective staging)
  • Requires optional message input or AI-generated message
  • Does not support partial commits or interactive rebases
When to use it

When you have made changes and want to commit them following conventional commit standards.

When not to use it

When you need to commit only specific changes or use a non-conventional message.

Security analysis

Safe
Quality score85/100

The skill only uses git commands to stage and commit changes. No destructive or exfiltrating actions are present.

No concerns found

Examples

Commit all changes
Commit my recent changes with a descriptive conventional commit message.
Commit with type feat
Please review my changes and commit them following conventional commit format with type feat.

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