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
6/2/2026
Claude Code
#git#commit-message#conventional-commits#dco

Recommended for

Automated summary

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

How this analysis is made

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/smart-git-commit-mm8o52bq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/smart-git-commit-mm8o52bq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/smart-git-commit-mm8o52bq/download' --output '.skill-downloads/smart-git-commit-mm8o52bq/SKILL.md.part' && mv '.skill-downloads/smart-git-commit-mm8o52bq/SKILL.md.part' '.skill-downloads/smart-git-commit-mm8o52bq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/smart-git-commit-mm8o52bq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills