Cline rules

1---
2description: "Guides Cline to perform thorough code reviews focused on bugs, security vulnerabilities, performance issues, and readability improvements."
3author: "Cline Team"
4version: "1.0"
5category: "Development"
6tags: ["code-review", "security", "performance", "best-practices"]
7globs: ["*.*"]
8---
9 
10# Code Review
11 
12When asked to review code, follow this structured approach to provide actionable, high-quality feedback.
13 
14## Review Process
15 
161. **Understand Context First** — Read the code and any related files to understand what it does and why before critiquing.
17 
182. **Prioritize Findings** — Organize feedback by severity:
19   - 🔴 **Critical** — Bugs, security vulnerabilities, data loss risks
20   - 🟡 **Important** — Performance issues, error handling gaps, logic problems
21   - 🟢 **Suggestions** — Readability, naming, style, simplification opportunities
22 
233. **Be Specific and Actionable** — Every piece of feedback should include:
24   - What the issue is
25   - Why it matters
26   - A concrete suggestion or fix
27 
28## What to Look For
29 
30### Correctness
31- Logic errors and off-by-one mistakes
32- Unhandled edge cases (null, empty, boundary values)
33- Race conditions in concurrent code
34- Incorrect assumptions about data shape or API contracts
35 
36### Security
37- Unsanitized user input (SQL injection, XSS, command injection)
38- Hardcoded secrets or credentials
39- Missing authentication or authorization checks
40- Insecure data handling (logging sensitive data, weak crypto)
41 
42### Performance
43- Unnecessary work inside loops (N+1 queries, repeated calculations)
44- Missing caching opportunities
45- Large memory allocations or leaks
46- Blocking operations that should be async
47 
48### Maintainability
49- Functions doing too many things
50- Duplicated logic that should be extracted
51- Unclear naming or missing context
52- Dead code or unused imports
53 
54### Error Handling
55- Swallowed exceptions with no logging
56- Missing error handling on I/O operations
57- Unclear error messages that won't help debugging
58- Missing cleanup in failure paths
59 
60## Output Format
61 
62Present findings grouped by severity. For each finding:
63- Reference the specific file and line/section
64- Explain the issue concisely
65- Suggest a fix with a code snippet when helpful
66 
67End with a brief summary of overall code quality and the most important action items.
68