Commit Message Assistant | Commit Message 助手

SkillCommunication

[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, 提交規範.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Commit Message Assistant | Commit Message 助手 skill

What this skill tells your AI

The instructions your AI receives, as published by asiaostrich/universal-dev-standards in skills/commit-standards/SKILL.md and read by ahel’s review.

Generate well-formatted commit messages following the Conventional Commits standard.

根據 staged 的變更,產生符合 Conventional Commits 格式的 commit message。

Workflow | 工作流程

  1. Detect language - Read .standards/manifest.json → check options.output_language. If not found, default to english.
  2. Check status - Run git status and git diff --staged to understand changes
  3. Analyze changes - Determine the type (feat, fix, refactor, etc.) and scope
  4. Generate message - Create a commit message following the format for the detected language (see below)
  5. Confirm and commit - Ask user to confirm before executing git commit

Message Format | 訊息格式

<type>(<scope>): <subject>

<body>

<footer>

Commit Types | 提交類型

TypeWhen to Use使用時機
featNew feature新功能
fixBug fix修復錯誤
refactorCode refactoring重構(無功能變更)
docsDocumentation文件更新
styleFormatting格式調整(無邏輯變更)
testTests測試相關
perfPerformance效能優化
choreMaintenance維護任務

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 #123 for 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 | 必須遵守的規則

  1. English body comes FIRST, Chinese body comes SECOND
  2. Separate English and Chinese body with a blank line
  3. NEVER mix languages within the same paragraph
  4. NEVER omit the Chinese body — both languages are required
  5. 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 #123

Traditional Chinese Format | 繁體中文格式

When output_language is traditional-chinese, use Chinese types and body:

功能(認證): 新增 OAuth2 Google 登入支援

實作 Google OAuth2 認證流程供使用者登入。

關閉 #123

Usage | 使用方式

  • /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 --report to submit feedback

Reference | 參考

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件:/commit

For complete AI agent behavior definition, see the corresponding command file: /commit

Signals

GitHub stars
73
Forks
13
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
commit-asiaostrich
Source
github.com/asiaostrich/universal-dev-standards