commit

Summarize git repository changes and generate Conventional Commit candidates.

27|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Renkunzhao/motion_viewer --skill commit-renkunzhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Renkunzhao/motion_viewer/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/Renkunzhao/motion_viewer --skill commit-renkunzhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of interpreting repository changes and crafting clear, standards-compliant commit messages by summarizing git diffs and producing ready-to-use Conventional Commits with limited scopes.

Core Features & Use Cases

  • Read-only repository inspection: Runs git status, git diff, and git diff --staged to collect the authoritative change set without modifying anything.
  • Change summarization in Chinese: Produces a file- and module-level summary that distinguishes behavior changes, refactors, and documentation edits.
  • Conventional Commit proposals: Generates three candidate commit messages using allowed types and restricted scopes (model, motion, ui) and explains the choice in Chinese; recommends splitting large changes across commits when beneficial.
  • Safety guardrails: Explicitly prohibits executing git commit, git push, or creating PRs without explicit user approval and prints exact commands to run if requested.

Quick Start

Summarize the current repository changes and propose three Conventional Commit messages scoped to model, motion, or ui, with one Chinese sentence explaining each choice.

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?

To generate Conventional Commit messages from git diff, the Skill inspects staged and unstaged changes using read-only git commands, summarizes file-level modifications, and proposes three scoped commit candidates. It explains each choice in Chinese and recommends splitting large changes if needed.

What is the best way to write Conventional Commits for code review summaries?

The best way to write Conventional Commits for code review summaries is to parse repository diffs and generate three message candidates restricted to model, motion, or ui scopes. The Skill produces file- and module-level summaries distinguishing behavior changes, refactors, and documentation edits.

Can I automatically commit changes after generating conventional commit messages?

No, you cannot automatically commit changes. The Skill enforces safety guardrails that explicitly prohibit executing git commit, git push, or creating PRs without explicit user approval. It only suggests exact commands to run if requested.

How do I summarize git repository changes for changelog notes?

To summarize git repository changes for changelog notes, the Skill runs git status and git diff to collect the authoritative change set, then produces a summary distinguishing behavior changes, refactors, and documentation edits to prepare commits and changelog notes.

What scopes are allowed when generating Conventional Commit candidates?

When generating Conventional Commit candidates, the allowed scopes are strictly limited to model, motion, or ui. The Skill uses allowed commit types and explains the choice for each candidate in Chinese.

Does this Conventional Commit generator support repositories with no staged changes?

Yes, the Conventional Commit generator supports repositories with no staged changes by running git status, git diff, and git diff --staged to collect all modifications. It summarizes both staged and unstaged changes to propose commit messages.