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
+14
View File
@@ -23,3 +23,17 @@ globs: [".cursor/**"]
## Security
- All `.cursor/` files must be scanned for hidden Unicode before committing (see cursor-security.mdc)
## Quality Thresholds (canonical reference)
All rules and skills must reference the single source of truth below. Do NOT restate different numeric thresholds in individual rule or skill files.
| Concern | Threshold | Enforcement |
|---------|-----------|-------------|
| Test coverage on business logic | 75% | Aim (warn below); 100% on critical paths |
| Test scenario coverage (vs AC + restrictions) | 75% | Blocking in test-spec Phase 1 and Phase 3 |
| CI coverage gate | 75% | Fail build below |
| Lint errors (Critical/High) | 0 | Blocking pre-commit |
| Code-review auto-fix | Low + Medium (Style/Maint/Perf) + High (Style/Scope) | Critical and Security always escalate |
When a skill or rule needs to cite a threshold, link to this table instead of hardcoding a different number.