Cursor rule

1---
2description: Code review guidelines and checklist for Compozy development
3globs:
4  - "**/*.go"
5  - "**/*.yaml"
6  - "**/*.yml"
7  - "**/Makefile"
8  - "**/*.md"
9alwaysApply: true
10---
11# Code Review Checklist
12 
13## Pre-Review Requirements
14 
15<pre_review_requirements>
16Before submitting code for review, ensure:
17- All tests pass and follow the established testing patterns
18- Code has been formatted with `go fmt`
19- All linter warnings have been addressed
20- Error handling follows project patterns
21- Security considerations have been addressed
22</pre_review_requirements>
23 
24## Review Checklist
25 
26<checklist type="code_review">
271. Does the code follow the established project structure and patterns?
282. Are errors handled appropriately and with context?
293. Is the code well-tested with both unit and integration tests?
304. Are interfaces used appropriately to define behavior?
315. Does the code pass all linter checks?
326. Is the code secure and performant?
337. Are dependencies injected properly?
348. Is context propagated correctly?
359. Is the code simple, readable, and maintainable?
36</checklist>
37 
38## Common Issues to Watch For
39 
40<common_issues type="code_quality">
41- Missing error handling or inappropriate error propagation
42- Tests that don't follow the `t.Run("Should...")` pattern
43- Hardcoded values that should be configurable
44- Missing context propagation in functions that make external calls
45- Security vulnerabilities like exposed secrets or unvalidated inputs
46- Performance issues like unnecessary allocations or inefficient algorithms
47- Code that doesn't follow established project patterns
48- Missing or inadequate test coverage
49</common_issues>
50 
51## Review Process
52 
53<review_process>
54- Focus on correctness, maintainability, and adherence to standards
55- Check for proper error handling and testing patterns
56- Verify security considerations have been addressed
57- Ensure code follows established project patterns and conventions
58- Look for opportunities to improve code clarity and efficiency
59</review_process>
60