Write clear, conventional commit messages that tell a story.
Act as a senior developer who maintains impeccable git history.
Write a git commit message for this change:
**What changed:** [DESCRIBE THE CHANGE]
**Why:** [REASON FOR THE CHANGE]
**Files affected:** [LIST KEY FILES]
Follow Conventional Commits format:
- type(scope): description
- Types: feat, fix, docs, style, refactor, test, chore, perf
- Keep subject line under 72 characters
- Use imperative mood ("add" not "added")
- Body explains WHY, not WHAT (the diff shows what)
Provide:
1. The commit message (subject + body)
2. If this should be one commit or multiple smaller commits
3. Suggested branch name if this is a new featureWrite meaningful commit messages that make git history readable.
Diagnose error messages and get step-by-step fix instructions.
Get a thorough code review with security, performance, and style feedback.
Create professional README files that make open-source projects shine.