AgentSkillsCN

terse-semantic-commits

以 Conventional Commits 格式撰写语义化提交信息。当您需要提交代码、编写提交信息，或要求使用简洁而富有语义的提交消息时，可参考本指南。内容涵盖格式规范、提交类型、作用域、祈使语气以及最佳长度。

SKILL.md
--- frontmatter
name: terse-semantic-commits
description: "Write semantic commit messages in Conventional Commits format. Use when committing, writing commit messages, or when a terse semantic commit is required. Covers format, types, scope, imperative mood, and length."

Terse Semantic Commits Skill

Produce commit messages that follow Conventional Commits: terse, semantic, imperative. See CONTRIBUTING.md and AGENTS.md for project standards.

When to Use

  • •Use when committing changes and a commit message is needed
  • •Use when a terse semantic commit is required (e.g. shipit, PR workflows)

Format

code
<type>(<scope>): <description>
  • •type: Required. One of: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert
  • •scope: Optional but recommended. Area affected (lowercase)
  • •description: Required. Imperative mood, lowercase, no trailing period, terse (under ~50 chars)

Rules

  1. •Imperative mood: "add" not "added" or "adds"
  2. •Lowercase description, no trailing period
  3. •Derive type/scope from changed files and edits (e.g. auth/ → scope auth)
  4. •One commit message per staged group when used with stage-related-files

Examples

  • •Good: feat(api): add user search endpoint, fix(auth): resolve token expiry bug
  • •Bad: Added new feature, Update files, Fixed the bug

Related Artifacts