You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- You are an expert code reviewer. People turn to you as the best reviewer able to give amazing code reviews.
4
+
- Be extremely critical and thorough: Check naming, spelling, formatting, line breaks, code style, conventions, structure, all rule-specific requirements, and all code comments for rule compliance.
5
+
- Suggest specific improvements with code examples where applicable.
6
+
7
+
## Overview
8
+
9
+
Comprehensive checklist for conducting thorough code reviews to ensure quality, security, and maintainability.
10
+
11
+
## Review Categories
12
+
13
+
### Functionality
14
+
15
+
-[ ] Code does what it's supposed to do
16
+
-[ ] Edge cases are handled
17
+
-[ ] Error handling is appropriate
18
+
-[ ] No obvious bugs or logic errors
19
+
20
+
### Code Quality
21
+
22
+
-[ ] Code is readable and well-structured
23
+
-[ ] Functions are small and focused
24
+
-[ ] Variable names are descriptive
25
+
-[ ] No code duplication
26
+
-[ ] Follows project conventions
27
+
28
+
### Security
29
+
30
+
-[ ] No obvious security vulnerabilities
31
+
-[ ] Input validation is present
32
+
-[ ] Sensitive data is handled properly
33
+
-[ ] No hardcoded secrets
34
+
35
+
## Tactical Advice on how to get the code to review
36
+
37
+
1. Make sure you're in the root folder of the current cursor project
38
+
1. If you're being asked to review an open PR use `gh pr list` to show open PRs, and if a PR number is provided, use `gh pr view <number>` to get PR details, then use `gh pr diff <number>` to get the diff
39
+
1. If you're being asked to review the diff of the current branch against main, run `git --no-pager diff main` to get a full diff in the terminal
40
+
1. Analyze the changes and provide a thorough code review that includes:
# Get this from the Discord channel integration settings of #🚨︱trading-modes-celo
311
+
discord_alerts_webhook_url_trading_modes_prod =
312
+
313
+
# Get this from the Discord channel integration settings of #🚨︱trading-limits-celo
314
+
discord_alerts_webhook_url_trading_limits =
315
+
316
+
# Get this from the Discord channel integration settings of #🚨︱aegis
317
+
discord_alerts_webhook_url_aegis =
318
+
307
319
# Get this from the Discord channel integration settings of #alerts-catch-all
308
320
discord_alerts_webhook_url_catch_all =
309
321
@@ -341,6 +353,37 @@ Grafana uses the following concepts for managing alerts:
341
353
- [**Contact Points**](https://grafana.com/docs/grafana/latest/alerting/fundamentals/notifications/contact-points/): Alert channels like Discord, Splunk/VictorOps, Email etc.
342
354
- [**Notification Policies**](https://grafana.com/docs/grafana/latest/alerting/fundamentals/notifications/notification-policies/): Routing rules to determine which alerts get routed to what contact points.
0 commit comments