AgentSkillsCN

mythosmud-commit-messages

根据Git差异生成符合Conventional Commits规范的提交信息：包含简短摘要、可选正文、类型（作用域）格式，并以#数字链接相关议题。适用于用户请求提交信息、需要修改或撰写提交、或在审查暂存变更时使用。

SKILL.md
--- frontmatter
name: mythosmud-commit-messages
description: Generate conventional commit messages from git diffs: short summary, optional body, type(scope) format, link issues with #number. Use when the user asks for a commit message, to amend or write commits, or when reviewing staged changes.

MythosMUD Commit Messages

Format

  • •First line: 50–72 characters, imperative mood or past tense. Type(scope): summary.
  • •Body (optional): Bullet points for detail. No corporate boilerplate.
  • •Issue link: Include #issue-number when the commit relates to an issue.

Types

TypeUse for
featNew feature
fixBug fix
docsDocumentation only
refactorCode change that neither fixes nor adds feature
testAdding or updating tests
choreBuild, tooling, deps

Template

code
<type>(<scope>): <short summary>

- Optional bullet for detail
- Another bullet if needed

#issue-number

Examples

Feature with issue:

code
feat(auth): add JWT login endpoint

Add POST /auth/login and token validation middleware.

#42

Bug fix:

code
fix(reports): correct date formatting in timezone conversion

Use UTC timestamps consistently across report generation.

Docs only:

code
docs(api): update OpenAPI spec for players endpoint

Rules

  • •Be direct and technical. Avoid phrases like "reflect our commitment" or "these changes ensure."
  • •Link issues when the work addresses an issue: add #issue-number in the body or after the summary.
  • •No trailing period on the subject line.
  • •Prefer past tense for summary when describing what was done (e.g. "added", "fixed", "updated").