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
229
229
4.**Each comment must reference exactly one Rule ID.**
230
230
5.**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.
231
-
6.**If no violations are found, output exactly** (with no quotes, markdown, or additional text):
231
+
6.**If no violations are found, create a comment** (with no quotes, markdown, or additional text):
232
232
LGTM :feelsgood:. Thank you for your hard work!
233
233
7.**Output LGTM if and only if**:
234
234
- You examined EVERY line of EVERY changed file
235
235
- You checked EVERY changed file against ALL rules
236
236
- You found ZERO violations matching the exact rule criteria
237
237
- You verified no false negatives by checking each rule systematically
238
-
If you found even ONE violation or have ANY uncertainty do NOT output LGTM - create inline comments instead.
238
+
If you found even ONE violation or have ANY uncertainty do NOT create LGTM comment - create inline comments instead.
239
239
8.**DO NOT invent new rules, stylistic preferences, or commentary outside the listed rules.**
240
-
9.**DO NOT describe what you are doing, output any summaries, explanations, extra content, comments on rules that are NOT violated or ANYTHING ELSE except from rules violations or LGTM message.**
240
+
9.**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.**
241
+
Only inline comments regarding rules violations or general comment with LGTM message are allowed.
241
242
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.
242
243
243
244
## Tool Usage Example
244
245
245
-
For each violation, call the tool like this:
246
+
For each violation, call the mcp__github_inline_comment__create_inline_comment tool like this.
247
+
CRITICAL: **DO NOT** use the Bash tool for inline comments:
0 commit comments