Skip to content

Latest commit

 

History

History
57 lines (43 loc) · 2.2 KB

git-commit-msg.md

File metadata and controls

57 lines (43 loc) · 2.2 KB

Git Commit Message Template

Usage

Supply this file to the AI to generate a git commit message based on changes since the last commit. For small changes, aim for 140 characters. For large changes (10+ files or 100+ lines), allow up to 300 characters.

Format

The AI should:

  1. Analyze the git diff to understand changes
  2. Create a concise commit message under 140 characters for small changes
  3. For large changes (10+ files or 100+ lines), allow up to 300 characters
  4. Use conventional commit format: type: description
  5. Focus on the most significant changes
  6. Use commas instead of dashes between items (per user preference)
  7. Prioritize the most impactful changes when space is limited

Commit Types

  • feat: New features
  • fix: Bug fixes
  • refactor: Code refactoring
  • docs: Documentation changes
  • style: Code style changes
  • test: Test changes
  • chore: Maintenance tasks
  • perf: Performance improvements
  • ci: CI/CD changes
  • build: Build system changes

Examples

Small Changes (under 140 chars)

  • refactor: remove duplicate metadata titles, update deps
  • feat: add user authentication, implement password reset
  • fix: resolve type errors, update component props
  • fix: host van detail route css, correct container width and image sizing

Large Changes (up to 300 chars)

  • feat: implement van state system with dynamic pricing, refactor components to use GenericComponent, add discount functionality, update schema with VanState enum and discount field, create VanPrice and VanBadge components, migrate to prisma.config.ts, enhance seed data with state management, update README with new features

Instructions for AI

  1. Run git diff to see unstaged changes
  2. Run git diff --cached to see staged changes
  3. Run git diff --stat to see change summary
  4. Analyze the changes and categorize them
  5. Count files changed and lines modified
  6. Generate a descriptive commit message:
    • Small changes (under 10 files, under 100 lines): aim for 140 characters
    • Large changes (10+ files or 100+ lines): allow up to 300 characters
  7. Use conventional commit format with appropriate type
  8. Focus on the most impactful changes
  9. Use commas instead of dashes between items