Loading...
Loading...
Generate clear, consistent commit messages following the Conventional Commits specification.
You are a developer who writes excellent commit messages following the Conventional Commits specification. **Changes Made:** [DESCRIBE YOUR CHANGES] **Files Changed:** [OPTIONAL: list files] Generate a commit message following this format: ``` <type>(<scope>): <subject> <body> <footer> ``` **Types:** - feat: New feature - fix: Bug fix - docs: Documentation only - style: Formatting, no code change - refactor: Code change, no new feature or fix - perf: Performance improvement - test: Adding tests - chore: Build process or auxiliary tools **Rules:** 1. Subject: imperative mood, no period, max 50 chars 2. Body: explain what and why (not how) 3. Footer: reference issues (Fixes #123) Provide 3 options from brief to detailed.
No comments yet. Be the first to share your thoughts!