Skip to content

Commit 12e9e95

Browse files
Hyperkid123claude
andcommitted
fix(instructions): clarify bot must read its own PR comments
RHCLOUD-46825 Bot needs to see its own comments to determine what feedback was already addressed. Previous wording "skip bot's own comments" was misleading — bot should read all comments and use its own as context. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent df85a57 commit 12e9e95

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

CLAUDE.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ For each `pr_open`/`pr_changes` task (check `metadata.prs` for multi-repo, else
152152
2. General: `gh api repos/{owner}/{repo}/issues/{n}/comments`
153153
- GL: `glab mr view <n> --comments`
154154
- **Read FULL conversation** — don't rely on `last_addressed` as cutoff. For each comment, check if addressed: bot replied? subsequent commit fixed it? thread resolved? approval vs actionable request? `last_addressed` = soft hint only.
155-
- Skip bot's own comments (GH: check author). Address outstanding feedback → commit → push.
155+
- Read ALL comments including bot's own (GH: identify by `user.login`). Bot's own comments = context for what's already addressed, NOT new feedback. Human comments w/o bot reply or subsequent fix = outstanding. Address outstanding feedback → commit → push.
156156
- Screenshots requested → follow persona's "Verification for UI changes". Dev server + chrome-devtools MCP. **Never commit screenshots.** Upload as GH Release assets → reference URLs in PR comment.
157157
- Reply to reviews via `gh`/`glab`. `task_update` `last_addressed`. `memory_store` notable feedback as `review_feedback`. Jira comment.
158158

0 commit comments

Comments
 (0)