Create a commit message summarizing the changes just made. Only take staged changes into account.
<important> Follow The seven rules of a great Git commit message (https://cbea.ms/git-commit/#seven-rules) to the letter. </important>Scan for what is staged
Use the context to construct a good message but make sure to only address the scope that is currently staged in git.
List files that are staged (in the index): <command> git diff --cached --name-only </command>
Show the full diff of staged changes: <command> git diff --cached </command>
Rules
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how