Skill Gallery
← Back to list
DauQuangThanh

git-commit

by DauQuangThanh

Agent Skills, Custom Agents and Corresponding Software Development Workflow Commands.

⭐ 2🍴 2📅 Jan 23, 2026
agentic-aiaiprocesssoftware-developmentspec-drivenspec-driven-development
View on GitHubRun in Manus

SKILL.md

name: git-commit description: Generates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions.

Git Commit

Generates well-structured git commit messages following conventional commit standards and best practices.

Key Principles

  1. Be specific: Describe exactly what changed
  2. Be consistent: Follow conventional commit format
  3. Be atomic: One logical change per commit
  4. Be clear: Write for others (including future you)
  5. Be complete: Include why and context when needed
  6. Be conventional: Follow standard format for automation

Standard Format

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

<body>

<footer>

Components:

  • type: Category of change (required) - feat, fix, docs, refactor, perf, test, build, ci, chore, style, revert
  • scope: Area affected (optional) - auth, api, ui, db, etc.
  • subject: Brief description (required, ≤50 chars)
  • body: Detailed explanation (optional, wrap at 72 chars)
  • footer: Breaking changes, issue refs (optional)

Basic Workflow

  1. Choose the commit type:

    • feat: New user-facing functionality
    • fix: Bug fix for users
    • docs: Documentation only
    • refactor: Code restructuring without behavior change
    • perf: Performance improvement
    • test: Adding/updating tests
    • build: Dependency/build system changes
    • ci: CI/CD configuration changes
    • chore: Maintenance tasks
    • style: Code formatting
    • revert: Reverting previous commit

  2. Write subject line (imperative mood, ≤50 chars):

    ✅ feat(auth): add OAuth2 authentication
✅ fix(api): resolve race condition in user updates
❌ feat: added some stuff
❌ fix: bug fix

  3. Add body if needed (explain why, not just what):

    • Required for breaking changes
    • Recommended for complex changes
    • Wrap lines at 72 characters

  4. Include footer:

    • Breaking changes: BREAKING CHANGE: description
    • Issue references: Closes #123, Fixes #456

Quick Examples

Simple feature:

feat(auth): add password reset endpoint

Bug fix with context:

fix(api): prevent null pointer in user preferences

User preferences API crashed when optional fields were null.
Added null checks and default values.

Closes #456

Breaking change:

feat(api)!: change response format to JSON:API spec

BREAKING CHANGE: API responses now follow JSON:API format.
Update client code to parse data from `data` key instead
of root level.

Closes #789

Reference Documentation

For detailed guidance, load these reference files as needed:

Score

Total Score

65/100

Based on repository quality metrics

✓SKILL.md

SKILL.mdファイルが含まれている

+20
✓LICENSE

ライセンスが設定されている

+10
○説明文

100文字以上の説明がある

0/10
○人気

GitHub Stars 100以上

0/15
✓最近の活動

1ヶ月以内に更新

+10
○フォーク

10回以上フォークされている

0/5
✓Issue管理

オープンIssueが50未満

+5
✓言語

プログラミング言語が設定されている

+5
✓タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon