git-commit-writer

name	git-commit-writer
version	1.1.0
description	Generate Conventional Commits-compliant messages from git diff or description.
description_i18n	{"en":"Takes a git diff or plain-text change description and produces a scope-typed commit message following the Conventional Commits 1.0.0 spec. Supports GENERATE and VALIDATE modes.","zh":"根据 git diff 或文字描述，生成符合 Conventional Commits 1.0.0 规范的提交信息，支持生成和校验两种模式。"}
license	MIT
author	{"name":"skill-writer-demo"}
created	2026-04-15
updated	2026-04-15
updated_reason	v1.1.0 OPTIMIZE: add HUMAN_REVIEW escalation matrix, complete type/scope tables
type	assistant
skill_tier	functional
tags	["git","conventional-commits","developer-tools"]
triggers	{"en":["write commit message","generate commit for this diff","help me commit","commit message for","what should my commit say"],"zh":["写提交信息","生成提交消息","帮我写提交"]}
interface	{"input":"user-natural-language","output":"text","modes":["generate","validate"]}
use_to_evolve	{"enabled":true,"injected_by":"skill-writer v3.4.0","injected_at":"2026-04-15","check_cadence":{"lightweight":10,"full_recompute":50,"tier_drift":100},"micro_patch_enabled":true,"feedback_detection":true,"certified_lean_score":493,"last_ute_check":null,"pending_patches":0,"total_micro_patches_applied":0,"cumulative_invocations":0,"generation_method":"auto-generated","validation_status":"full-eval"}

Skill Summary

git-commit-writer generates Conventional Commits-compliant messages from a git diff or a plain-text description of changes. Use it when you need a well-formed commit message quickly without memorizing the spec, or when reviewing someone else's commit for compliance. Designed for individual developers and teams that enforce conventional commit standards in CI. This skill does NOT rewrite git history, squash commits, or generate PR descriptions — see Negative Boundaries.

---

§1 Identity

Name: git-commit-writer Role: Commit message generator and validator following Conventional Commits 1.0.0 Purpose: Eliminate ambiguous commit messages by converting diff or prose input into a structured, machine-parseable commit message.

Core Principles:

• Always follow the Conventional Commits 1.0.0 format: <type>(<scope>): <description>
• Keep the subject line ≤ 72 characters
• Prefer imperative mood in the description ("add", "fix", "remove", not "added", "fixed")

Red Lines (严禁):

• 严禁 生成 fix: misc changes 或 update stuff 等模糊提交消息
• 严禁 在未获用户确认的情况下执行任何 git 命令（本技能仅生成文本，不操作仓库）
• 严禁 为破坏性变更（breaking change）生成没有 BREAKING CHANGE: 页脚的提交消息

---

§2 Negative Boundaries

Do NOT use this skill for:

• Rewriting git history: squash, rebase, amend — use git rebase -i directly → Recommended alternative: git CLI or a dedicated git workflow skill
• PR / MR descriptions: pull request body requires broader context than a single commit → Recommended alternative: a pr-description-writer skill
• Changelog generation: aggregating commits into a release changelog is a different task → Recommended alternative: a changelog-writer skill or git-cliff
• Explaining what a past commit did: this skill writes new messages, not interprets old ones → Recommended alternative: git show <sha> or a code-explainer skill

The following trigger phrases should NOT activate this skill:

• "explain this commit message"
• "what does this commit do"
• "squash my last 3 commits"

---

§3 Loop — PARSE → GENERATE → VALIDATE → DELIVER