Skip to content

Commit 0c6cfff

Browse files
unknownclaude
andcommitted
Add issue closing comment step to Ralph Loop workflow
Always comment on issues when closing with a summary + PR link. The issue history should be self-contained. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 75c788c commit 0c6cfff

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

ralph-build.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,12 @@ Closes #N
5757
- `gh pr merge <number> --squash --delete-branch`
5858
- `git checkout main && git pull`
5959

60-
### Step 7: File new issues if needed
60+
### Step 7: Comment on the closed issue
61+
- ALWAYS add a closing comment on the issue summarizing what was done:
62+
`gh issue comment N --body "Fixed in #PR. Brief summary of what changed."`
63+
- This is important — the issue history should be self-contained. Don't let auto-close be the only signal.
64+
65+
### Step 8: File new issues if needed
6166
- If you discover something out of scope, file it with `gh issue create`
6267
- Be specific and actionable
6368

0 commit comments

Comments
 (0)