AgentSkillsCN

git-commit-message

利用 Anchor 框架（v0.32.1）与 Next.js 前端，完整构建 Solana 区块链项目，涵盖 Rust 智能合约、测试用例以及钱包集成等功能。适用于开发 Solana dApp、NFT 市场、代币发行项目、DAO 组织、DeFi 协议，或当用户提及 Solana、Anchor 或区块链相关项目时。

SKILL.md
--- frontmatter
name: git-commit-message
description: Generate Conventional Commits git commit messages from the staged diff. Use this when the user asks to craft a commit message or when preparing a commit.

Conventional Commit Message Authoring

Use this skill when the user asks for a git commit message (for example: “craft commit message”, “write commit message”, “conventional commit”).

Output contract

Return a commit message in Conventional Commits format.

  • •Subject line format: <type>(<scope>): <subject>
  • •Scope: optional but preferred when obvious
  • •Subject: imperative, present tense; no trailing period; keep it short

If useful, add a body separated by a blank line. The body should explain why and notable behavior changes, not a code dump.

When the staged change spans multiple areas (for example: UI change + dependency updates + tooling/docs), omit scope and add a short body summarizing the main buckets of change.

Allowed types

  • •feat: a new feature
  • •fix: a bug fix
  • •docs: documentation-only changes
  • •style: formatting/whitespace (no logic)
  • •refactor: code change that neither fixes a bug nor adds a feature
  • •perf: performance improvement
  • •test: adding/fixing tests
  • •build: build system or external dependencies
  • •ci: CI configuration/scripts
  • •chore: other changes that don’t modify product code
  • •revert: revert a previous commit

Procedure

  1. •Inspect the actual change (prefer staged changes when available; otherwise use the working tree diff).
  2. •Choose type based on intent.
  3. •Choose scope as the smallest meaningful area (examples: auth, chat, ui, api, deps, build, tests).
  4. •Write a single clear subject describing the change.
  5. •If multiple distinct concerns are included, propose splitting commits; otherwise add a short body (1–6 lines) that summarizes the key parts.
  6. •If the change introduces a breaking change, add ! after type/scope and include a BREAKING CHANGE: footer.

Examples

Simple UI affordance

code
feat(auth): add cancel button to registration form

Bug fix with brief rationale

code
fix(chat): prevent duplicate broadcast on reconnect

Avoids emitting a second join event when the socket reconnects.

Breaking change

code
feat(api)!: rename /v1/messages to /v1/chat-messages

BREAKING CHANGE: Clients must call /v1/chat-messages instead of /v1/messages.