You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
31 lines
1.2 KiB
31 lines
1.2 KiB
---
|
|
description:
|
|
globs:
|
|
alwaysApply: true
|
|
---
|
|
use system date command to timestamp all interactions with accurate date and time
|
|
python script files must always have a blank line
|
|
remove whitespace at the end of lines
|
|
never git add or commit for me. always preview changes and commit message to use and allow me to copy and paste
|
|
✅ Preferred Commit Message Format
|
|
|
|
Short summary in the first line (concise and high-level).
|
|
Avoid long commit bodies unless truly necessary.
|
|
|
|
✅ Valued Content in Commit Messages
|
|
|
|
Specific fixes or features.
|
|
Symptoms or problems that were fixed.
|
|
Notes about tests passing or TS/linting errors being resolved (briefly).
|
|
|
|
❌ Avoid in Commit Messages
|
|
|
|
Vague terms: “improved”, “enhanced”, “better” — especially from AI.
|
|
Minor changes: small doc tweaks, one-liners, cleanup, or lint fixes.
|
|
Redundant blurbs: repeated across files or too generic.
|
|
Multiple overlapping purposes in a single commit — prefer narrow, focused commits.
|
|
Long explanations of what can be deduced from good in-line code comments.
|
|
|
|
Guiding Principle
|
|
|
|
Let code and inline documentation speak for themselves. Use commits to highlight what isn't obvious from reading the code.
|
|
|