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
**IMPORTANT**: Always refer to the `AGENTS.md` file in the root directory for comprehensive project guidelines, coding standards, and architectural decisions.
3
+
## Review Philosophy
4
+
5
+
- Only comment when you have HIGH CONFIDENCE (>80%) that an issue exists
6
+
- Be concise: one sentence per comment when possible
7
+
- Focus on actionable feedback, not observations
8
+
- When reviewing text, only comment on clarity issues if the text is genuinely confusing or could lead to errors.
9
+
"Could be clearer" is not the same as "is confusing" - stay silent unless HIGH confidence it will cause problems
10
+
11
+
## Priority Areas (Review These)
12
+
13
+
### Security & Safety
14
+
15
+
- Unsafe code blocks without justification
16
+
- Command injection risks (shell commands, user input)
17
+
- Path traversal vulnerabilities
18
+
- Credential exposure or hardcoded secrets
19
+
- Missing input validation on external data
20
+
- Improper error handling that could leak sensitive info
21
+
22
+
### Correctness Issues
23
+
24
+
- Logic errors that could cause panics or incorrect behavior
25
+
- Resource leaks (files, connections, memory)
26
+
- Off-by-one errors or boundary conditions
27
+
- Optional types that don't need to be optional
28
+
- Booleans that should default to false but are set as optional
29
+
- Overly defensive code that adds unnecessary checks
30
+
- Unnecessary comments that just restate what the code already shows (remove them)
31
+
32
+
### Architecture & Patterns
33
+
34
+
- Code that violates existing patterns in the codebase
35
+
- Missing error handling
36
+
- Code that is not following [Python PEP8](https://peps.python.org/pep-0008/) guidelines.
37
+
38
+
## Project-Specific Context
39
+
40
+
- See [AGENTS.md](../AGENTS.md) in the root directory for project guidelines and architecture decisions.
41
+
42
+
## CI Pipeline Context
43
+
44
+
**Important**: You review PRs immediately, before CI completes. Do not flag issues that CI will catch.
45
+
46
+
### What Our CI Checks
47
+
48
+
-`.github/workflows/test-python.yaml` - linting, unit, and integration tests
49
+
-`.github/workflows/test-e2e.yaml` - e2e tests
50
+
51
+
## Skip These (IMPORTANT)
52
+
53
+
Do not comment on:
54
+
55
+
-**Style/formatting** - CI handles this (ruff, ty, uv)
56
+
-**Test failures** - CI handles this (full test suite)
57
+
-**Missing dependencies** - CI handles this
58
+
59
+
## Response Format
60
+
61
+
When you identify an issue:
62
+
63
+
1.**State the problem** (1 sentence)
64
+
2.**Why it matters** (1 sentence, only if not obvious)
65
+
3.**Suggested fix** (code snippet or specific action)
66
+
67
+
## When to Stay Silent
68
+
69
+
If you're uncertain whether something is an issue, don't comment. False positives create noise and reduce trust in the review process.
0 commit comments