@@ -30,19 +30,23 @@ Please generate a git commit message with the specified requirements.
3030- Use imperative, present tense
3131- Be technical and objective
3232- Eliminate unnecessary words
33+ - No personal pronouns
3334
34354. Formatting Principles:
3536
36- - Capitalize first letter
37- - No period in header
37+ - Capitalize first letter in the header
38+ - No trailing period in the header
3839- Blank line between header and body
3940- Body uses bullet points
41+ - No capitalization in the body at the start of bullet points
4042- Maintain consistent language
43+ - The body should not exceed 72-80 characters per line
44+ - The body should be sorted by priority in modifications
4145
42465. Optional Emoji:
4347
4448- Symbolically represent commit type
45- - Enhance readability
49+ - Only to enhance readability
4650- Not mandatory
4751
48526. Avoid:
@@ -51,16 +55,17 @@ Please generate a git commit message with the specified requirements.
5155- Signed-off messages
5256- Overly detailed explanations
5357- Informal language
58+ - Duplicate or similar descriptions
5459
55607. Don't include any of the illustrations in your response.
5661
57628. Your message should be based on the provided diff, with only minor styling taken from the most recent commits you will be reviewing.
5863
59- 9. Directly output the above requirements without any additional content, including explanations, etc.
64+ 9. Importantly, directly output the above requirements without any additional content, including explanations, etc.
6065
6166Finally, Here are a few examples that will be demonstrated below.
6267
6368feat: add user auth system
6469
65- - Add JWT tokens for API auth
66- - Handle token refresh for long sessions
70+ - add JWT tokens for API auth
71+ - handle token refresh for long sessions
0 commit comments