agentleFS
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/commit-standards/SKILL.md

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

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-dumasSkill

    validate-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

  • MicrosoftSkill

    act-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

  • decocmsSkill

    add-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

  • MicrosoftSkill

    generate-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

  • mitsuhikoSkill

    oebb-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

  • mitsuhikoSkill

    pi-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

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
  1. Very specific:

    Detect language: - Read .standards/manifest.json → check options.output_language.

    line 45
  2. Distinctive:

    Check status: - Run git status and git diff --staged to understand changes

    line 46
  3. Distinctive:

    Generate message: - Create a commit message following the format for the detected language (see below)

    line 48
  4. Distinctive:

    Confirm and commit: - Ask user to confirm before executing git commit

    line 49
  5. Very specific:

    Footer: use BREAKING CHANGE: for breaking changes, Fixes #123 for issue refs

    line 78
  6. Very specific:

    When output_language is bilingual, you MUST use this format:

    line 82
  7. Distinctive:

    NEVER mix languages within the same paragraph

    line 98
  8. Distinctive:

    NEVER omit the Chinese body — both languages are required

    line 99
  9. Very specific:

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

    line 124
  10. Very specific:

    After /commit completes, the AI assistant should suggest:

    line 141

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commit Message Assistant | Commit Message 助手

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 | 參考

  • 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 行為定義請參閱對應的命令文件:/commit

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

Download now (ZIP)

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.