cursor-tdd-rules — Cursor Rules

Before committing, follow these steps: • Review Current State: Check status, differences, and history in one command `bash # Combined command for efficiency - check status, differences, and recent history export GIT_PAGER=cat && git status && echo "=== CHANGES ===" && git diff && echo "=== RECENT COMMITS ===" && git log --oneline -5 ` • Analyze Changes and Suggest Commit Strategy: Based on the degree of file changes, decide whether to split into multiple commits Analysis Criteria: • Single commit: If changes belong to the same logical function or modification scope • Multiple commits: If changes involve multiple different functions, file types, or modification purposes Situations requiring multiple commits: • Simultaneously modified API and frontend components • Contains both new features and bug fixes (different types of changes) • Modified code in multiple different modules • Simultaneously performing feature addition and code refactoring • Contains both documentation updates and program logic modifications AI Behavior: • If suggesting multiple commits, must: • List suggested commit groupings • Provide suggested message format for each commit • List files that should be included in each commit • Stop execution, wait for user confirmation or adjustment suggestions • If judged as single commit, continue with subsequent steps Suggestion Format Example: ` Suggested split into 2 commits: Commit 1: Add user authentication API • Files: services/auth/auth.api.ts, services/auth/auth.types.ts • Message: feat(auth): add user authentication API Commit 2: Update project configuration • Files: package.json, tsconfig.json • Message: chore: update TypeScript configuration Please confirm whether to proceed with this suggestion, or tell me your adjustments. ` • Add Files: Add files to staging area and confirm `bash # For specific files git add filename && git status # For all changed files (only when confirmed as single commit) git add . && git status ` • Commit and Verify: Use Conventional Commits format for committing and verify result `bash git commit -m "type(scope): description" && git status && git log --oneline -3 `

Feature Development ` feat(auth): add user authentication API feat(ui): implement login form validation feat: add password reset functionality ` Bug Fixes ` fix(api): resolve login timeout issue fix(ui): correct form validation error display fix: prevent memory leak in data processing ` Documentation Updates ` docs: update API documentation docs(readme): add installation instructions ` Refactoring ` refactor(auth): simplify token validation logic refactor: extract common utility functions ` Testing ` test(auth): add unit tests for login API test: improve test coverage for user service ` Build and Configuration ` chore: update dependencies to latest versions chore(config): update TypeScript configuration build: add Docker support for development ` Performance Improvements ` perf(api): optimize database query performance perf: reduce bundle size by 20% ` CI/CD ` ci: add automated testing workflow ci: update deployment configuration `

This document outlines the complete workflow and message format specifications for AI-performed Git commits.

Single Commit Workflow `bash