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
First, run `uv run prek run --from-ref origin/main` to check for linting/formatting issues on files changed in this PR.
60
+
61
+
If there are any issues:
62
+
- For SAFE auto-fixable issues (formatting, import sorting, trailing whitespace, etc.), run `uv run prek run --from-ref origin/main` again to auto-fix them
63
+
- Stage the fixed files with `git add`
64
+
- Commit with message "style: auto-fix linting issues"
65
+
- Push the changes with `git push`
66
+
67
+
Do NOT attempt to fix:
68
+
- Type errors that require logic changes
69
+
- Complex refactoring suggestions
70
+
- Anything that could change behavior
71
+
72
+
## STEP 2: Review the PR
73
+
74
+
${{ github.event.action == 'synchronize' && 'This is a RE-REVIEW after new commits. First, get the list of changed files in this latest push using `gh pr diff`. Review ONLY the changed files. Check ALL existing review comments and resolve ones that are now fixed.' || 'This is the INITIAL REVIEW.' }}
75
+
76
+
Review this PR focusing ONLY on:
77
+
1. Critical bugs or logic errors
78
+
2. Security vulnerabilities
79
+
3. Breaking API changes
80
+
4. Test failures (methods with typos that wont run)
81
+
82
+
IMPORTANT:
83
+
- First check existing review comments using `gh api repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/comments`. For each existing comment, check if the issue still exists in the current code.
84
+
- If an issue is fixed, use `gh api --method PATCH repos/${{ github.repository }}/pulls/comments/COMMENT_ID -f body="✅ Fixed in latest commit"` to resolve it.
85
+
- Only create NEW inline comments for HIGH-PRIORITY issues found in changed files.
86
+
- Limit to 5-7 NEW comments maximum per review.
87
+
- Use CLAUDE.md for project-specific guidance.
88
+
- Use `gh pr comment` for summary-level feedback.
89
+
- Use `mcp__github_inline_comment__create_inline_comment` sparingly for critical code issues only.
90
+
91
+
## STEP 3: Coverage analysis
92
+
93
+
Analyze test coverage for changed files:
94
+
95
+
1. Get the list of Python files changed in this PR (excluding tests):
0 commit comments