Enhance coding standards and testing rules

- Updated coderule.mdc to emphasize readability, meaningful comments, and maintainability.
- Revised testing.mdc to set a 75% coverage threshold for business logic and clarified expected results requirements.
- Improved clarity in git-workflow.mdc regarding commit message formatting and length.
- Added completeness audit requirements in research steps and quality checklists to ensure thoroughness in test specifications.

Made-with: Cursor
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-04-17 20:28:55 +03:00
parent bead15f492
commit c51cb9b4a5
17 changed files with 275 additions and 90 deletions
+3 -2
View File
@@ -5,6 +5,7 @@ alwaysApply: true
# Git Workflow
- Work on the `dev` branch
- Commit message format: `[TRACKER-ID-1] [TRACKER-ID-2] Summary of changes`
- Commit message total length must not exceed 30 characters
- Commit message subject line format: `[TRACKER-ID-1] [TRACKER-ID-2] Summary of changes`
- Subject line must not exceed 72 characters (standard Git convention for the first line). The 72-char limit applies to the subject ONLY, not the full commit message.
- A commit message body is optional. Add one when the subject alone cannot convey the why of the change. Wrap the body at 72 chars per line.
- Do NOT push or merge unless the user explicitly asks you to. Always ask first if there is a need.