commit-draft

Generate conventional-commit messages from git status, diff, and log outputs.

2|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/Max-Loo/multi-chat --skill commit-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-draft
Source: https://github.com/Max-Loo/multi-chat/tree/main/.opencode/skills/commit-draft
Command: npx skills add https://github.com/Max-Loo/multi-chat --skill commit-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

为当前工作区中尚未提交的代码或文档变更生成简短、规范的提交信息,帮助保持版本历史清晰可读。

Core Features & Use Cases

  • 自动分析 git status、diff 与 log,推断变更范围与风格偏好。
  • 支持按提交类型前缀(feat、fix、docs 等)自动分组与格式化。
  • 提供分组确认流程,确保在多变更场景下选择提交范围后再生成信息。

Quick Start

请对当前工作区中的未提交变更提出需求,助手将生成一个符合约定的 commit message。

Frequently Asked Questions about commit-draft

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

FAQPage Schema
How do I generate conventional commit messages for uncommitted Git changes?

To generate conventional commit messages for uncommitted Git changes, the Skill analyzes your git status, diff, and log outputs to infer change scope and style. It then formats a standardized message with type, scope, and a 50-character limit.

What is the best way to group multiple code changes before writing a Git commit message?

The best way to group multiple code changes before writing a Git commit message is through a confirmation process. The Skill provides guardrails for grouping and confirmation, ensuring you select the correct commit scope before message generation.

Does this tool enforce the 50-character limit for conventional commit messages?

Yes, this tool enforces the 50-character limit for conventional commit messages. It automatically formats outputs with type, scope, and subject constraints to ensure your version-control history remains concise and standardized.

Can I use commit-draft to analyze Git log history and match my existing commit style?

Yes, you can use commit-draft to analyze Git log history and match your existing commit style. It evaluates prior log outputs to infer your style preferences and apply them to newly generated conventional commit messages.