Smart Git Commit

VerifiedSafe

Create well-structured Git commits with conventional commit format. Automatically analyzes staged or unstaged changes and generates commit messages with type, scope, body, and signed-off-by. Helps maintain DCO compliance by requiring signed-off-by.

Sby Skills Guide Bot
DevelopmentIntermediate
906/2/2026
Claude Code
#git#commit-message#conventional-commits#dco

Recommended for

Our review

Creates a well-structured Git commit with a conventional commit message and DCO sign-off.

Strengths

  • Automatically formats commit messages in conventional commit style
  • Analyzes staged changes to suggest type and scope
  • Ensures DCO compliance by adding a Signed-off-by line

Limitations

  • Requires files to be staged or modified
  • May not capture deep business context
  • Enforces a strict format that might not fit all projects
When to use it

Use this skill when you need to create a commit with a descriptive, convention-compliant message.

When not to use it

Do not use this skill when you want a custom, non-conventional commit message or when you need to skip DCO certification.

Security analysis

Safe
Quality score90/100

The skill uses Bash to run git status and git diff, which is standard and non-destructive for commit analysis. No exfiltration or malicious commands.

No concerns found

Examples

Commit staged changes
Commit my staged changes with a suitable message.
Specify commit message
/commit Add user authentication feature
Commit with analysis
I've made some changes, please commit them with a conventional commit message.

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