GG

    Git 提交信息生成 · Git Commit Message Generator

    1

    按变更内容生成规范提交信息:类型、范围、要点与破坏性变更标注。 Turn a change description into a Conventional Commit message with type, scope, key points, and breaking-change flags.

    $7

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more
    GG

    Git 提交信息生成 · Git Commit Message Generator

    Example session with this skill installed

    请为「支付模块增加支付宝渠道并修复退款回调超时」生成规范提交信息。

    • Read your context and instructions
    • Compiled the git git commit

    Git 提交信息已生成。

    推荐

    feat(payment): add Alipay channel and fix refund callback timeout

- add Alipay channel with signature verification
- fix refund callback timeout by extending timeout to 10s

BREAKING CHANGE: callback payload now includes channel field

    备选(拆分提交)

    fix(payment): extend refund callback timeout to 10s

    feat(payment): add Alipay channel

    Next steps

    1. 按团队规范选择单条或拆分提交。
    2. 关联 issue 编号后推送。

    Connects securely to your tools. The creator never sees your data.

    What you get

    Standardize commit history using Conventional Commits.Identify breaking changes and scopes for release notes.Generate bilingual commit messages for global teams.Draft concise summaries for squash merges.

    About this skill

    它解决什么问题

    提交历史记录充满了诸如“修复”或“更新”之类的模糊消息，使得评论、发布和代码追溯（blame）毫无用处。

    这个技能做什么

    • 从更改摘要写入Conventional Commit 规范提交信息。
    • 检测类型、范围和破坏性变更。
    • 建议使用正文要点来说明原因和方法。
    • 提供squash 合并的替代方案。

    为什么比裸提示词强

    它强制执行消息框架：类型、范围、摘要、正文、破坏性变更，因此历史记录保持可读并且工具可以解析它。

    典型用例

    • 为功能分支编写消息。
    • 标准化整个团队的消息。
    • 从提交历史记录中准备发行说明。

    局限

    它总结了您所描述的变化；它不会读取您的差异。

    English · 英文介绍

    The problem

    Commit history fills with vague messages like 'fix' or 'update', making reviews, releases, and blame useless.

    What it does

    • Writes Conventional Commit style messages from a change summary.
    • Detects type, scope, and breaking changes.
    • Suggests body bullets for the why and the how.
    • Provides alternatives for squash merges.

    Why this beats prompting it yourself

    It enforces a message frame: type, scope, summary, body, breaking, so history stays readable and tooling can parse it.

    Use cases

    • Writing messages for a feature branch.
    • Standardizing messages across a team.
    • Preparing release notes from commit history.

    Known limitations

    It summarizes the changes you describe; it does not read your diff.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    Frequently Asked Questions