Repository navigation
feat(issue-auto-implement): add .comment_body for no-change and request-clarification PR comments - #253
Merged
Conversation
…st-clarification PR comments - When implement makes no code changes, Claude writes the PR comment body to .comment_body (no-change rationale or request for clarification). Workflow posts it on the PR instead of claiming 'commit(s) pushed'. - Track changes_pushed in implement-verify loop; use conditional PR comment (Claude's text or generic fallback when no .comment_body). - Implement prompt: optional path to write .comment_body for (a) no-change scenarios or (b) when more information is needed. - ensureMetaFiles: skip defaults when .comment_body exists. Reset .comment_body in git so it is never committed. - .gitignore and AGENTS.md: document .comment_body and Request more info vs comment body from implement. Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the implement step runs but Claude makes no code changes (e.g. feedback is a question, current approach is preferred, or clarification is needed), the workflow was still posting "Addressed review feedback. New commit(s) pushed" — which was misleading.
Changes
.comment_bodyfile: When Claude decides not to make code changes, it writes the PR comment body to.github/actions/issue-auto-implement/.comment_body(one or two sentences). Used for: (a) no-change scenarios (thank the reviewer, briefly explain), or (b) when more information is needed (e.g. "Could you clarify whether you want X or Y?"). The workflow posts this on the PR and appends "Verification passed."changes_pushedtracking: The implement-verify loop setschanges_pushed=trueonly when a commit was actually pushed. The "Comment on PR" step uses this to choose the message: commits pushed vs. Claude's.comment_bodyor a generic fallback..comment_bodyinstead of.commit_msgwhen making no code changes.ensureMetaFilesskips defaults when.comment_bodyexists..comment_bodyin git so it is never committed; read it when posting the no-change comment..gitignoreand AGENTS.md document the file and the "Request more info vs comment body from implement" distinction.Branch was created from origin/main in a new worktree so this PR contains only these four files (no other CLI or gateway changes).
Made with Cursor