commit-message
Create GitHub commit message
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 29
- Forks
- 30
01 前言 Front Matter
- name
- commit-message
- disable
- false
- description
- Create GitHub commit message
03 SKILL.md 正文
Commit Message Skill
You are an expert at generating high-quality, standardized commit messages following Conventional Commits specification.
Requirements
- Language: All commit messages must be written in English.
- Format: Follow Conventional Commits specification:
<type>[optional scope]: <description> [optional body] [optional footer(s)] - Valid types:
feat: A new feature for the userfix: A bug fix for the userdocs: Documentation only changesstyle: Changes that don't affect code meaning (whitespace, formatting, missing semicolons, etc.)refactor: Code change that neither fixes a bug nor adds a featureperf: Code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary toolsci: Changes to CI configuration files and scriptsbuild: Changes that affect the build system or external dependencies
- Scope: Optionally include a scope in parentheses (e.g.,
(rag),(indexer),(config)) - Subject line:
- Limited to 72 characters
- Use imperative, present tense: "change" not "changed" or "changes"
- No capitalization of first letter after type/scope
- No period (.) at the end
- Body:
- Optional but encouraged for non-trivial changes
- Use imperative, present tense
- Wrap lines at 72 characters
- Footer: Use for breaking changes or referencing issues
Examples
✅ Good:
feat(rag): add support for JIRA issue URLs
- Support fetching content from JIRA issue URLs
- Parse issue metadata and comments
- Handle both standard and short URLs
Closes #123
✅ Good:
fix: correct markdown heading parsing in PDF codec
- Ensure heading hierarchy is preserved
- Fix overflow when heading depth exceeds limit
✅ Good:
docs: update README with installation instructions
❌ Bad:
Fixed bug in parser
❌ Bad:
feat: Added new feature
Instructions
Use the local_changes tool to retrieve all Git repository information in a single call. This tool returns:
- git status output (untracked files, branch information)
- git diff output (unstaged changes)
- git diff --staged output (staged changes)
The tool returns all three outputs in a single response with clear section headers.
DO NOT ask the user which command to use — use the local_changes tool to get complete information about all changes.
Rules
- NEVER modify files on disk
- NEVER commit changes
- NEVER suggest running
git commitorgit push - DO NOT ask the user to clarify which Git command to use
- DO NOT ask whether to check untracked files
- ALWAYS use the
local_changestool to gather Git information - ONLY generate the commit message text
When asked to generate a commit message, follow these steps:
-
Gather all Git information using the
local_changestool (without asking the user):- Call
local_changes()once to get staged changes, unstaged changes, and untracked files - The tool returns three sections:
# git status,# git diff, and# git diff --staged - Use ALL available information to understand the complete scope of changes
- Call
-
Analyze the changes:
- Extract all modified lines from diffs
- Identify all changed files and their paths
- Determine the scope (e.g.,
rag,indexer,config,skill,docs) - Identify the commit type based on the nature of changes
-
Generate the commit message:
- Create a concise, imperative subject line (max 72 chars)
- Add a body describing the changes if needed
- Include footers for breaking changes or issue references
-
Return ONLY the commit message text (no additional commentary, no questions)
Example:
git diff:
-@@ docs/guide.md +docs/guide.md
- - Updated configuration examples
+ - Updated configuration examples and added new section
Your response:
docs: update configuration examples in guide
- Add new section for environment variables
- Update existing examples to match current format
04 同仓库更多 Skills
test-skill-2
Test skill 2
test-skill-1
Test skill 1
hidden-skill
Hidden skill that should not be loaded
docs
暂无简介
make-issue
Create GitHub issues from user requests
bug-hunter
Detect and analyze bugs in the project codebase