You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- ALWAYS when fixing lint or test failures prefer to do the minimal amount of changes to fix the issues
165
165
- USE single-line commit messages under 50 chars; use conventional commit messages template format: `feat: add something new`
166
166
- USE `git diff HEAD sourceFilePath` to diff an uncommitted file against the last commit
167
-
- ALWAYS run `git status` to check ALL uncommitted changes after completing any code edits, then provide exactly 3 commit message suggestions covering the ENTIRE uncommitted diff
167
+
- NEVER capitalize words in commit messages
168
+
- ALWAYS run `git status` to check ALL uncommitted changes after completing any code edits, then reply with 3 commit message suggestions covering the ENTIRE uncommitted diff
168
169
- ALWAYS check existing code patterns before implementing new features
169
170
- USE existing extensions and utilities rather than creating new ones
170
171
- ALWAYS consider applying YAGNI (You Ain't Gonna Need It) principle for new code
0 commit comments