commit-message
Use when drafting or reviewing commit messages or pull request titles for this repository.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- commit-message
- description
- Use when drafting or reviewing commit messages or pull request titles for this repository.
03 SKILL.md 正文
Commit Message
Follow the format in Commit Messages & Pull Requests.
- Base the message on the supplied changes or diff. When asked for a message
for staged changes, inspect
git diff --cachedand summarize only that scope. - Choose the type that describes the change, using the repository's vocabulary:
feat,fix,chore,refactor,test, ordoc. - Use either the affected domain or a known ticket ID in parentheses. The
|in the format means either option; do not include it literally. If no ticket is provided, use the domain or affected area rather than inventing an ID. - Write a short, lower-case description of the concrete change. Preserve a ticket ID's spelling when using it as the scope.
- When asked only for a message or title, return the proposed line without commentary. Drafting a message does not itself authorize a commit or PR.
Examples:
feat(accounts): add account creation endpoint
fix(3442): correct ledger balance calculation
doc(agents): add commit message skill
04 同仓库更多 Skills
testing
Use when adding, changing, or reviewing tests in this repository.
reporting-usecase-creation
Use when creating, changing, or reorganizing reporting use cases and their DTOs, read queries, tests, wiring, or HTTP endpoints. Does not cover accounting reporting-period or reporting-context management.
pr-reviewer
Use when reviewing code changes, pull requests, or branch diffs.
planner
Use whenever the user asks for a plan, implementation plan, approach, roadmap, or planning, and whenever the agent decides to create or present a plan before doing work.
pair-programmer
Use when implementing code changes in this repository.
migration
Use when creating, running, or reviewing database migrations.