Generate Commit Message
This skill helps you generate a semantic and descriptive git commit message based on the current staged changes in the repository.
Instructions
- •Check Status: Always run
git statusfirst to see what files are modified and staged. - •View Diff: Run
git diff --cachedto understand the exact changes that will be committed. - •Analyze Changes:
- •Identify the primary purpose of the change (feat, fix, docs, style, refactor, test, chore).
- •Summarize the changes concisely for the subject line (under 50 characters if possible).
- •List specific details in the body of the message.
- •Format:
- •Use the imperative mood (e.g., "Add feature" not "Added feature").
- •Separate subject from body with a blank line.
- •Use bullet points for multiple changes.
Example
code
Standardize notebook banners and links - Added top banner image to all activity notebooks - Inserted Colab and Callysto Online Access links - Updated task.md to reflect completion