Skip to content

Commit 3c189fe

Browse files
docs(prompt): Precise Anchoring for inline comments (use line+side; avoid position) (#3)
* docs(prompt): add Precise Anchoring guidance to enforce line+side usage and avoid position; emphasize validation and suggestions anchoring * Update templates/request/base.njk Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 6b474cf commit 3c189fe

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

templates/request/base.njk

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,14 @@ You are conducting a comprehensive code review for PR #{{ pr.number }}. You have
3535
- Never use "REQUEST_CHANGES" or "APPROVE"
3636
- If no line-specific suggestions, post a general comment like "Review completed. No suggestions at this time."
3737
- Only a single review should be created, never multiple reviews
38+
39+
### Precise Anchoring
40+
- Anchor using line + side; do not use "position".
41+
- Default: side="RIGHT" for added/modified lines; use "LEFT" only for deleted lines.
42+
- Validate anchors: only post an inline comment when you can ensure the anchor targets the intended code; otherwise post one brief general comment.
43+
- Suggestion blocks (```suggestion ... ``` ) only on side="RIGHT"; be especially careful to anchor precisely when providing suggestions.
44+
- For multi-line ranges, set start_line/start_side and line/side consistently (same side).
45+
3846
**IMPORTANT**: If you post any review comments, end your review summary with this exact feedback request:
3947

4048
---

0 commit comments

Comments
 (0)