commit

Generate conventional Git commit messages with Chinese descriptions from staged changes.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/xjiang77/agent-wisp --skill commit-xjiang77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/xjiang77/agent-wisp/tree/main/tools/setup-toolkit/skills/commit
Command: npx skills add https://github.com/xjiang77/agent-wisp --skill commit-xjiang77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating structured git commits with conventional commit messages, reducing manual effort and ensuring consistent descriptions across projects.

Core Features & Use Cases

  • Automated Commit Message: Generate conventional commit messages from diffs and staged changes, with Chinese descriptions.
  • Guided Workflow: Enforces type, scope, and breaking change indicators to standardize history.
  • Use Case: When you review changes and want to commit only selectively, this skill helps craft precise messages and record why changes were made.

Quick Start

Run the commit workflow to generate a conventional commit with a Chinese description for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages with Chinese descriptions for git changes?

You can automate conventional commit generation with Chinese descriptions by analyzing git diffs and staged changes. This skill enforces a deterministic workflow that drafts messages with type, scope, and breaking change indicators before verifying and committing.

What is the standard workflow for committing selective files with a conventional commit format?

The standard workflow for committing selective files follows deterministic stages: gather context, analyze changes, stage specific files, draft the conventional message, commit, and verify. This ensures precise messages record why changes were made across your project history.

Can I use this conventional commit workflow in a bash shell environment without extra dependencies?

Yes, this conventional commit workflow runs in a bash shell environment with no external dependencies. It directly processes git diffs and staged changes to produce structured commit messages with Chinese descriptions.

Does the automated commit message generation support type and scope indicators for breaking changes?

Yes, automated commit message generation enforces type, scope, and breaking change indicators to standardize git history. It applies these conventional commit format rules while generating Chinese descriptions from analyzed code diffs.

What are the limitations of automating git commits with Chinese descriptions?

Automating git commits with Chinese descriptions depends entirely on diff quality and staged changes provided. The deterministic workflow requires clear context gathering to accurately draft conventional commit formats without manual intervention.