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
-`body`: Concise and actionable description of the violation and fix, following the below Comment Format
249
249
6.**Each comment must reference exactly one Rule ID.**
250
250
7.**Output must consist exclusively of calls to mcp__github_inline_comment__create_inline_comment in the required format.** No other text, Markdown, or prose is allowed.
251
-
8.**If no violations are found, create a comment** (with no quotes, markdown, or additional text):
252
-
LGTM 👍 Thank you for your hard work!
253
-
9.**Output LGTM if and only if**:
251
+
8.**If no violations are found, add a reaction to the PR**:
252
+
Add a 👍 (+1) reaction to the PR body using the `.github/scripts/addPrReaction.sh` script.
253
+
9.**Add reaction if and only if**:
254
254
- You examined EVERY changed line in EVERY changed file (via diff + targeted grep/read)
255
255
- You checked EVERY changed file against ALL rules
256
256
- You found ZERO violations matching the exact rule criteria
257
257
- You verified no false negatives by checking each rule systematically
258
-
If you found even ONE violation or have ANY uncertainty do NOT create LGTM comment - create inline comments instead.
258
+
If you found even ONE violation or have ANY uncertainty do NOT add the reaction - create inline comments instead.
259
259
10.**DO NOT invent new rules, stylistic preferences, or commentary outside the listed rules.**
260
260
11.**DO NOT describe what you are doing, create comments with a summary, explanations, extra content, comments on rules that are NOT violated or ANYTHING ELSE.**
261
-
Only inline comments regarding rules violations or general comment with LGTM message are allowed.
261
+
Only inline comments regarding rules violations are allowed. If no violations are found, add a reaction instead of creating any comment.
262
262
EXCEPTION: If you believe something MIGHT be a Rule violation but are uncertain, err on the side of creating an inline comment with your concern rather than skipping it.
body: '<Body of the comment according to the Comment Format>'
274
274
```
275
275
276
-
If ZERO violations are found, use the Bash tool to create a top-level PR comment.:
276
+
If ZERO violations are found, use the Bash tool to add a reaction to the PR body:
277
277
278
278
```bash
279
-
gh pr comment --body 'LGTM :feelsgood:. Thank you for your hard work!'
279
+
.github/scripts/addPrReaction.sh <PR_NUMBER>
280
280
```
281
281
282
-
**IMPORTANT**: When using the Bash tool, always use **single quotes** (not double quotes) around content arguments.
283
-
284
-
Example:
285
-
```bash
286
-
# Good
287
-
gh pr comment --body 'Use `useMemo` to optimize performance'
288
-
289
-
# Bad
290
-
gh pr comment --body "Use `useMemo` to optimize performance"
291
-
```
282
+
**IMPORTANT**: Always use the `.github/scripts/addPrReaction.sh` script instead of calling `gh api` directly. This script provides a secure, restricted interface that only allows adding +1 reactions to PRs, preventing arbitrary GitHub API calls.
0 commit comments