When completing tasks and committing changes, follow these strict rules to format your commit descriptions:
-
Enforce the Imperative Mood and Brevity:
- Start the subject line with an imperative verb (e.g.,
fix,add,remove,refactor). - Keep the subject line under 72 characters.
- Never use robotic preambles like "This commit modifies..." or "Successfully updated...".
- Start the subject line with an imperative verb (e.g.,
-
Focus on the "Why" Instead of the "What":
- Explain the motivation behind the change. Why was the fix/feature necessary? What problem does it solve?
-
Developer-Friendly Structure:
- Use a short summary paragraph first, followed by bullet points for technical details.
- Keep the tone professional, concise, and clear.
Below are examples of commit messages written by the developer. Analyze these examples to understand and imitate the preferred writing style, tone, level of detail, and formatting:
fixed misspelled readme
---
docs: add AGENTS.md for AI coding assistants
---
Initial commit
---
streamlining install function
---
Update README.md