Smart Git Commit

VerifiedSafe

Creates well-structured commit messages by analyzing changes and following conventional commits format.

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

Recommended for

Our review

This skill helps create well-structured Git commits following the conventional commits format.

Strengths

  • Automatically generates properly formatted commit messages that follow standards.
  • Analyzes changes to choose the appropriate commit type (feat, fix, etc.).
  • Includes automatic DCO signing (Signed-off-by) to validate contributions.
  • Improves project maintainability by enforcing versioning best practices.

Limitations

  • Requires the user to have configured their Git name and email for the signature.
  • May not correctly detect scope or type for very heterogeneous changes.
  • Does not handle complex merge or revert scenarios.
When to use it

Use this skill when you need to commit changes and want a clear, standardized commit message that complies with DCO.

When not to use it

Avoid using it for commits that require a very detailed or non-standard description, or when you prefer to write the message manually.

Security analysis

Safe
Quality score85/100

The skill only runs non-destructive git status and diff commands to analyze repo changes. No exfiltration, modification, or dangerous shell commands are used.

No concerns found

Examples

Commit staged changes
Commit my changes with a message describing the bug fix for login validation.
Commit unstaged modifications
Generate a commit message for the current unstaged modifications.

description: Smart Git Commit when_to_use: When user asks to commit changes or run /commit user_invocable: true argument_hint: "[commit message]" allowed_tools:

  • Bash
  • Read
  • Grep priority: 10

Smart Git Commit

You are a Git commit expert. Help the user create a well-structured commit.

Instructions

  1. First, run git status to see what files are staged/modified
  2. Run git diff --cached to see staged changes (or git diff for unstaged)
  3. Analyze the changes and create a commit message following conventional commits format:
    • feat: for new features
    • fix: for bug fixes
    • docs: for documentation
    • refactor: for code refactoring
    • test: for adding tests
    • chore: for maintenance tasks

Commit Message Format

<type>(<scope>): <short description>

<body - explain what and why>

Signed-off-by: <用户名> <邮箱>

重要

  • 必须使用 Signed-off-by 而非 Co-Authored-By
  • 禁止添加任何 AI 生成标记
  • DCO 验证必须通过

User Request

$ARGUMENTS

Related skills