git-commit

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git-commit" with this command: npx skills add dauquangthanh/hanoi-rainbow/dauquangthanh-hanoi-rainbow-git-commit

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:

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Coding

code-quality-review

No summary provided by upstream source.

Repository SourceNeeds Review
-32
dauquangthanh
Coding

backend-code-review

No summary provided by upstream source.

Repository SourceNeeds Review
-16
dauquangthanh
Coding

frontend-code-review

No summary provided by upstream source.

Repository SourceNeeds Review
-12
dauquangthanh