commit
Skill4 starsChanged 28 days agoMITView on GitHub
[UDS] Generate commit messages that follow Conventional Commits, including the bilingual format. Use when: writing a commit message for staged changes, choosing a type and scope, producing a bilingual English and 中文 subject and body. Not for: deciding whether the change is ready to commit — use /checkin; aggregating commits into release notes — use /changelog. Keywords: commit message, Conventional Commits, feat, fix, refactor, scope, bilingual, 提交訊息, 雙語 commit, 提交規範.
- Commits and pushes
188 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- daledesilva/obsidian_inktheir own version, first seen Nov 9, 2026
- thoughtbot/rails-consultanttheir own version, first seen Nov 8, 2026
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- denysdovhan/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use validate-plan, act-on-feedback and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
shawn-dumasSkillvalidate-plan
Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.
Also in 5 projects that use this
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 3 projects that use this
decocmsSkilladd-mcp-tools
Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration
Also in 3 projects that use this
MicrosoftSkillgenerate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Also in 3 projects that use this
mitsuhikoSkilloebb-scotty
Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.
Also in 3 projects that use this
mitsuhikoSkillpi-share
Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.
Also in 3 projects that use this
Other versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- AsiaOstrich/universal-dev-standards★ 8427% same
Wrote their own version · 187
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- windmill-labs/windmill★ 18ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
177 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Detect language: - Read .standards/manifest.json → check options.output_language.
- Distinctive: line 46
Check status: - Run git status and git diff --staged to understand changes
- Distinctive: line 48
Generate message: - Create a commit message following the format for the detected language (see below)
- Distinctive: line 49
Confirm and commit: - Ask user to confirm before executing git commit
- Very specific: line 78
Footer: use BREAKING CHANGE: for breaking changes, Fixes #123 for issue refs
- Very specific: line 82
When output_language is bilingual, you MUST use this format:
- Distinctive: line 98
NEVER mix languages within the same paragraph
- Distinctive: line 99
NEVER omit the Chinese body — both languages are required
- Very specific: line 124
When output_language is traditional-chinese, use Chinese types and body:
- Very specific: line 141
After /commit completes, the AI assistant should suggest:
“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit Message Assistant | Commit Message 助手
Generate well-formatted commit messages following the Conventional Commits standard.
根據 staged 的變更,產生符合 Conventional Commits 格式的 commit message。
Workflow | 工作流程
- Detect language - Read
.standards/manifest.json→ checkoptions.output_language. If not found, default toenglish. - Check status - Run
git statusandgit diff --stagedto understand changes - Analyze changes - Determine the type (feat, fix, refactor, etc.) and scope
- Generate message - Create a commit message following the format for the detected language (see below)
- Confirm and commit - Ask user to confirm before executing
git commit
Message Format | 訊息格式
<type>(<scope>): <subject>
<body>
<footer>Commit Types | 提交類型
| Type | When to Use | 使用時機 |
feat | New feature | 新功能 |
fix | Bug fix | 修復錯誤 |
refactor | Code refactoring | 重構(無功能變更) |
docs | Documentation | 文件更新 |
style | Formatting | 格式調整(無邏輯變更) |
test | Tests | 測試相關 |
perf | Performance | 效能優化 |
chore | Maintenance | 維護任務 |
Rules | 規則
- Subject: imperative mood, no period, first letter capitalized, ≤ 72 characters
- Body: explain WHY the change was made, not just what changed
- Footer: use
BREAKING CHANGE:for breaking changes,Fixes #123for issue refs
Bilingual Format | 雙語格式
When output_language is bilingual, you MUST use this format:
<type>(<scope>): <English subject>. <中文主旨>.
<English body — explain what and why in English>
<中文本文 — 用中文說明做了什麼及為什麼>
<footer>MUST Rules | 必須遵守的規則
- English body comes FIRST, Chinese body comes SECOND
- Separate English and Chinese body with a blank line
- NEVER mix languages within the same paragraph
- NEVER omit the Chinese body — both languages are required
- Footer (BREAKING CHANGE, Fixes #, Co-authored-by) goes LAST after both bodies
Bilingual Example | 雙語範例
feat(auth): Add OAuth2 Google login support. 新增 OAuth2 Google 登入支援.
Implement Google OAuth2 authentication flow for user login.
- Add Google OAuth2 SDK integration
- Create callback endpoint for OAuth flow
- Store refresh tokens securely
實作 Google OAuth2 認證流程供使用者登入。
- 整合 Google OAuth2 SDK
- 建立 OAuth 流程回呼端點
- 安全儲存更新權杖
Closes #123Traditional Chinese Format | 繁體中文格式
When output_language is traditional-chinese, use Chinese types and body:
功能(認證): 新增 OAuth2 Google 登入支援
實作 Google OAuth2 認證流程供使用者登入。
關閉 #123Usage | 使用方式
/commit- Auto-analyze staged changes and suggest commit message/commit fix login bug- Generate message based on provided description
Next Steps Guidance | 下一步引導
After /commit completes, the AI assistant should suggest:
提交完成。建議下一步 / Commit complete. Suggested next steps:
- 執行
git push推送到遠端 ⭐ Recommended / 推薦 — Push to remote- 準備發布時 → 執行
/changelog+/release— When preparing a release → Run/changelog+/release- 發現重複模式或規範摩擦 → 執行
/audit --report回報 — Patterns or friction detected → Run/audit --reportto submit feedback
Reference | 參考
- Conventional Commits Guide — Read it when you need the exact type, scope and format rules.
- Output Language Options — Read it when deciding which language a commit message is written in.
- Detailed guide: guide.md
- Core standard: commit-message-guide.md
AI Agent Behavior | AI 代理行為
完整的 AI 行為定義請參閱對應的命令文件:
/commitFor complete AI agent behavior definition, see the corresponding command file:
/commit
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

