When using this skill you must read the AGENTS.md to understand the general project guidelines.
- Check code changes
- Use
git diffto check the unstaged changes - Use
git diff HEADto see all the changes in this branch for extra context if necessary
- See
git log --oneline -40to see some other commit messages as example. - Analyze the benefits, reasoning, motivation for those changes to be made
- Do not spend too much tim with this, we want to have a quick reasponse unless requested by the user
- Output must be the commit message that the user must use
- Commit messages must be 1 compact line
- Append an optional '##' tag change is relevant for the release notes
- If there's important information that must be included, add an unordered enumeration with
-below the first line with them
Extra rules:
- Do not use emojis
- Describe what users will notice now works or no longer breaks.
- Lead with a direct verb such as
Fix,Add,Remove,Keep,StoporDon't. - Name the outcome in a few words, like
Don't leak relocs in corrupted bflts,Generate Windows types sdbs onceorFix shift overflow and ASR sign extension. - Tag crash and memory-safety fixes
##crash. - Avoid internal design terms and vague jargon.
- Use one natural line under 70 characters.
- This is a read-only operation, do not change or touch any file
- Output must be at least below 70 columns
- Use a casual writing style inspired in the other commits you saw in main
- If you find reasons to consider this change not mergeable into master let it know to the user
- Use capital text colorful or change just report it in the output with capital and colorful emojis