AGENTS.md (1145B)
1 ## Commit message 2 3 You are an expert at writing Git commits. Your job is to write a short clear commit message that summarizes the changes. 4 5 If you can accurately express the change in just the subject line, don't include anything in the message body. Only use the body when it is providing *useful* information. 6 7 Don't repeat information from the subject line in the message body. 8 9 Only return the commit message in your response. Do not include any additional meta-commentary about the task. Do not include the raw diff output in the commit message. 10 11 Follow good Git style: 12 13 - Separate the subject from the body with a blank line 14 - Try to limit the subject line to 50 characters 15 - Capitalize the subject line 16 - Do not end the subject line with any punctuation 17 - Use the imperative mood in the subject line 18 - Wrap the body at 72 characters 19 - Keep the body short and concise (omit it entirely if not useful) 20 21 ## Name Rule 22 23 Function and variable names should be concise and clearly indicate their function. 24 In particular, names that are relative to the timeline and unrelated to the program's semantics, such as "Fixed," are strictly prohibited.