commit

Summarize git working tree changes and draft three Conventional Commit messages.

56|5|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/K-h-Huang/Motion_Editor --skill commit-k-h-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/K-h-Huang/Motion_Editor/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/K-h-Huang/Motion_Editor --skill commit-k-h-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you summarize your current code changes and draft Conventional Commit messages so your Git history stays clear, consistent, and review-friendly.

Core Features & Use Cases

  • Read-only git state summarization: Uses git status and diff outputs to understand what changed across the repo without performing any commit actions.
  • Chinese, file/module-based change reporting: Organizes a summary by file/module and distinguishes behavior changes from refactors vs docs updates.
  • Conventional Commit message proposal: Produces 3 candidate commit messages with scopes limited to model|motion|ui to match team conventions.
  • Safety guardrails: Avoids running any commit/push commands and explicitly prevents PR creation without approval.

Quick Start

Ask the assistant to run the commit helper to summarize the current git changes and propose three Conventional Commit messages with scopes limited to model, motion, or ui.

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 from git diff output?

To generate Conventional Commit messages from git diff, the Skill analyzes your staged and working tree diffs to produce a Chinese file-level change summary and three candidate commit messages. It uses read-only git commands to safely inspect repository changes.

What is the best way to automate commit message generation for model, motion, or UI changes?

Automating commit message generation for model, motion, or UI changes involves analyzing git diffs and proposing messages strictly scoped to those domains. This Skill provides three Conventional Commit candidates organized by module to maintain a consistent and review-friendly git history.

Can I use this to summarize code changes without performing an actual git commit?

Yes, you can summarize code changes without committing, as the Skill operates using read-only git commands like git status and git diff. It includes safety guardrails that explicitly prevent executing commit, push, or PR creation commands without your approval.

Does this commit message generator support change summarization for both staged and unstaged files?

Yes, the commit message generator supports change summarization for both staged and unstaged files by running git diff and git diff --staged. It distinguishes behavior changes from refactors and documentation updates to provide an accurate repository change report.

What are the limitations of using automated Conventional Commit suggestions for code review workflows?

A key limitation is that automated Conventional Commit suggestions are restricted to scopes of model, motion, or ui, which may not fit all projects. The Skill also cannot execute the actual commit or automatically create pull requests, requiring manual developer approval.