Agent Skills › lnikell/loopndroll › git-commit

git-commit

GitHub

根据 Conventional Commits 规范分析代码变更，智能暂存文件并生成语义化提交信息。支持自动检测类型与范围、交互式覆盖及安全协议，确保提交标准化。

.agents/skills/git-commit/SKILL.md lnikell/loopndroll

Trigger Scenarios

用户要求提交代码变更用户提及 /commit 命令

Install

npx skills add lnikell/loopndroll --skill git-commit -g -y

More Options

Non-standard path

npx skills add https://github.com/lnikell/loopndroll/tree/main/.agents/skills/git-commit -g -y

Use without installing

npx skills use lnikell/loopndroll@git-commit

指定 Agent (Claude Code)

npx skills add lnikell/loopndroll --skill git-commit -a claude-code -g -y

安装 repo 全部 skill

npx skills add lnikell/loopndroll --all -g -y

预览 repo 内 skill

npx skills add lnikell/loopndroll --list

SKILL.md

Frontmatter

{
    "name": "git-commit",
    "license": "MIT",
    "description": "Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions \"\/commit\". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type\/scope\/description overrides, (4) Intelligent file staging for logical grouping",
    "allowed-tools": "Bash"
}

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>
EOF
)"