What happened
Issue #1789 (add action hints to review bot comments) was created May 19, before the fullsend-ai/agents repo was created on June 26. PR #2775 by rh-hemartin implemented the feature by modifying 4 files under internal/scaffold/fullsend-repo/. The review agent posted a COMMENTED review with 5 valid but non-blocking code-quality findings on June 30. Human reviewer ralphbean requested changes on July 6, noting the content has moved to fullsend-ai/agents. The PR was closed without merge on July 8. The author created a follow-up PR (fullsend-ai/agents#53) on the same day. Issue #1789 remains open with good-fullsend-issue, triaged, and priority/medium labels, still pointing at the fullsend repo with no cross-reference to the agents repo or PR #53.
What could go better
Issue #1789 retains labels that could trigger code agent dispatch (good-fullsend-issue, triaged) in the fullsend repo. Without a redirect, an agent or contributor could repeat the mistake. The retro for PR #2381 identified this exact risk pattern — issue #2378 retained ready-to-code after its PR was closed, creating a futile re-dispatch risk (documented in issue #3160). Confidence is high that this is a real risk given 3 instances of the pattern in 8 days.
Proposed change
Update issue #1789 with: (1) a comment noting that implementation should target fullsend-ai/agents (not internal/scaffold/fullsend-repo/), (2) a cross-reference to the active follow-up PR fullsend-ai/agents#53, and (3) removal of the good-fullsend-issue label (or addition of a label indicating the work belongs in another repo) to prevent code agent dispatch in the fullsend repo.
Validation criteria
Issue #1789 has a comment or body edit pointing to fullsend-ai/agents as the implementation target. The good-fullsend-issue label is removed or the issue is closed once fullsend-ai/agents#53 merges. No future PRs in fullsend attempt to implement this issue.
Generated by retro agent from #2775
What happened
Issue #1789 (add action hints to review bot comments) was created May 19, before the
fullsend-ai/agentsrepo was created on June 26. PR #2775 byrh-hemartinimplemented the feature by modifying 4 files underinternal/scaffold/fullsend-repo/. The review agent posted a COMMENTED review with 5 valid but non-blocking code-quality findings on June 30. Human reviewerralphbeanrequested changes on July 6, noting the content has moved tofullsend-ai/agents. The PR was closed without merge on July 8. The author created a follow-up PR (fullsend-ai/agents#53) on the same day. Issue #1789 remains open withgood-fullsend-issue,triaged, andpriority/mediumlabels, still pointing at the fullsend repo with no cross-reference to the agents repo or PR #53.What could go better
Issue #1789 retains labels that could trigger code agent dispatch (
good-fullsend-issue,triaged) in the fullsend repo. Without a redirect, an agent or contributor could repeat the mistake. The retro for PR #2381 identified this exact risk pattern — issue #2378 retainedready-to-codeafter its PR was closed, creating a futile re-dispatch risk (documented in issue #3160). Confidence is high that this is a real risk given 3 instances of the pattern in 8 days.Proposed change
Update issue #1789 with: (1) a comment noting that implementation should target
fullsend-ai/agents(notinternal/scaffold/fullsend-repo/), (2) a cross-reference to the active follow-up PR fullsend-ai/agents#53, and (3) removal of thegood-fullsend-issuelabel (or addition of a label indicating the work belongs in another repo) to prevent code agent dispatch in the fullsend repo.Validation criteria
Issue #1789 has a comment or body edit pointing to
fullsend-ai/agentsas the implementation target. Thegood-fullsend-issuelabel is removed or the issue is closed once fullsend-ai/agents#53 merges. No future PRs in fullsend attempt to implement this issue.Generated by retro agent from #2775