Skill Store 33

Commit

Create a well-structured commit with conventional format and proper git identity

by seabbs · MIT

The skill

Create a well-structured commit with conventional format and proper git identity

Create a well-structured commit.

Read git identity from the project's or org's CLAUDE.md ## Automation config table (bot_account, bot_email, owner_account, owner_email).

Arguments

  • --as-me: Commit as the owner instead of the bot account
  • --bot-only: Commit as the bot account without co-author

Git Identity

Mode Git Author Co-author
(default) bot account (bot_email) owner (owner_email)
--as-me owner (owner_email) none
--bot-only bot account (bot_email) none

Process

  1. Set git identity based on arguments:

    • Default or --bot-only: git config user.name "<bot_account>" and git config user.email "<bot_email>"
    • --as-me: git config user.name "<owner_account>" and git config user.email "<owner_email>"
  2. Review and commit changes:

    • Review staged and unstaged changes
    • Determine commit type (feat, fix, docs, style, refactor, perf, test, build, ci, chore)
    • Stage relevant files (exclude temp/generated: *.html, *.pdf, build/, *.log, .DS_Store)
    • Write concise commit message in conventional format: type(scope): description
    • Never push directly to main
  3. Add co-author trailer (default mode only):

    • Append Co-authored-by: <owner_account> <<owner_email>> to commit message

Auto-Exit When Standalone

IMPORTANT: If this command is being run as a standalone request, automatically exit after completing all phases successfully.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: seabbs/commit-79722656035.

Download SKILL.md · Markdown version

Details

Publisher
seabbs
Category
Software Development › Source control & code review
License
MIT
Updated
2026-08-25

References

More from seabbs