skills.rest
lldwb
lldwbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-create

Organizes working tree changes into single-responsibility local git commits with Chinese messages.

1|Updated Sep 11, 2026
Search Tags:#git#workflow#code review#version control#commit#conventional commits#staging
One-click install
npx skills add https://github.com/lldwb/lldwb-claude-skills --skill commit-create-lldwb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-create
Source: https://github.com/lldwb/lldwb-claude-skills/tree/main/skills/commit-create
Command: npx skills add https://github.com/lldwb/lldwb-claude-skills --skill commit-create-lldwb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing code changes often results in messy, mixed-purpose commits, vague messages, accidentally staged files, or leaked secrets. This Skill standardizes the entire local git commit workflow so every commit is clean, reviewable, and follows project conventions. ## Core Features & Use Cases - Single-Responsibility Splitting: Reviews git status and git diff, groups changes by module, and splits them into separate commits only when they are truly independent. - Safe Staging & Verification: Uses explicit git add <file> (never -A or .), re-checks staged content with git diff --staged, and blocks commits containing secrets, local artifacts, or sensitive paths. - Conventional Chinese Commit Messages: Writes Conventional Commits style messages with a ≤50-character title, blank-line-separated body, and optional emoji prefixes, type/scope overrides, trailers, and --amend for unpushed branches. - Use Case: After finishing a bug fix plus an unrelated formatting pass, ask the agent to commit; it will produce two separate commits with proper Chinese messages and verify each one with git show --stat. ## Quick Start Ask the agent to review the current working tree changes and commit them to the local repository with properly split, conventional Chinese commit messages.

Frequently Asked Questions about commit-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split git changes into multiple commits by module?▼

Review git status and git diff, group files by functional module or change theme, then stage and commit each group separately with explicit git add commands. Changes within one module stay in a single commit; only independent modules are split.

How to write conventional commit messages in Chinese?▼

Use the format type(scope): title with the first line under 50 characters, a blank line, then a body with verb-led bullet points under 72 characters per line. Write multi-line messages to a file and commit with git commit -F to preserve blank lines.

Why should I avoid git add -A or git add . when committing?▼

Blanket staging commands can silently include unrelated files, local build artifacts, or files containing credentials. Explicitly adding each file with git add <file> and verifying with git diff --staged prevents accidental inclusion.

Can I amend the previous commit with new changes?▼

Yes, use git commit --amend -F with a message file, but only on local branches that have not been pushed. Rewriting already-pushed history is not allowed without explicit user consent due to its irreversible impact.

What happens if the repository is mid-rebase or has a detached HEAD?▼

The workflow stops and reports the state instead of committing blindly. For rebase or merge in progress it suggests resolving conflicts or aborting first; for detached HEAD it asks whether to switch to a branch before committing.

Does this workflow push commits or create pull requests?▼

No, it only creates local commits and never pushes, merges, or opens pull requests automatically. Creating merge requests is delegated to a separate mr-create skill, keeping the commit step's scope strictly local.

Related Skills

Explore More Software Engineering Skills→
JoeCP17JoeCP17
8

test-driven-development

Enforce a test-first workflow with failing tests before production changes.

Community
Intermediate
koumatsumotokoumatsumoto

km:github-workflow

Automate GitHub branch creation, review, commit, push, and pull request workflows.

Community
Intermediate
whincwhinc
39

commit-work

Inspect working tree changes, stage them selectively, and generate Conventional Commits messages.

Community
Advanced
latestaiagentslatestaiagents
5

rebase-safely

Guides Git rebase operations with conflict resolution and recovery via reflog.

Official
Advanced