Added WARNING about heredoc syntax in step 4 of the review process
Added tea pulls clean <number> to step 5 after merging
Agent already references gitea skill via frontmatter which documents the heredoc limitation
Test Plan
Spawn code-reviewer on a test PR
Verify comment is posted (not backgrounded)
Verify branch is cleaned up after merge
## Summary
Fixes two bugs in the code-reviewer agent discovered during spawn-issues orchestration:
1. Heredoc syntax with `tea comment` causes backgrounding and silent failure
2. Missing branch cleanup after merging PRs
Closes #62
## Changes
- Added WARNING about heredoc syntax in step 4 of the review process
- Added `tea pulls clean <number>` to step 5 after merging
- Agent already references gitea skill via frontmatter which documents the heredoc limitation
## Test Plan
- [ ] Spawn code-reviewer on a test PR
- [ ] Verify comment is posted (not backgrounded)
- [ ] Verify branch is cleaned up after merge
This is an automated review generated by the code-reviewer agent.
Summary
This PR correctly addresses both bugs in the code-reviewer agent: the heredoc syntax issue causing silent failures and the missing branch cleanup after merging PRs. The fixes are minimal, targeted, and complete.
Findings
Code Quality
Changes are clear and well-documented
The WARNING in step 4 is prominently placed inline with the command usage
Practical alternatives are provided (concise comments or literal newlines)
The cleanup step is properly sequenced after merging in step 5
Potential Bugs
No issues found - the fixes directly address the reported bugs
Security Concerns
No security concerns identified
Style Notes
Consistent with existing agent prompt format
Good use of bold formatting for emphasis on the WARNING
Proper markdown structure maintained
Test Coverage
Test plan covers both fixes (comment posting and branch cleanup)
Manual verification approach is appropriate for agent behavior testing
Verdict
LGTM
All three acceptance criteria are met:
Agent now explicitly warns against heredoc syntax with tea comment
Branch cleanup with tea pulls clean added after merge
Gitea skill already referenced via frontmatter (line 7)
The fixes are minimal, correct, and ready to merge.
## AI Code Review
> This is an automated review generated by the code-reviewer agent.
### Summary
This PR correctly addresses both bugs in the code-reviewer agent: the heredoc syntax issue causing silent failures and the missing branch cleanup after merging PRs. The fixes are minimal, targeted, and complete.
### Findings
#### Code Quality
- Changes are clear and well-documented
- The WARNING in step 4 is prominently placed inline with the command usage
- Practical alternatives are provided (concise comments or literal newlines)
- The cleanup step is properly sequenced after merging in step 5
#### Potential Bugs
- No issues found - the fixes directly address the reported bugs
#### Security Concerns
- No security concerns identified
#### Style Notes
- Consistent with existing agent prompt format
- Good use of bold formatting for emphasis on the WARNING
- Proper markdown structure maintained
#### Test Coverage
- Test plan covers both fixes (comment posting and branch cleanup)
- Manual verification approach is appropriate for agent behavior testing
### Verdict
**LGTM**
All three acceptance criteria are met:
1. Agent now explicitly warns against heredoc syntax with tea comment
2. Branch cleanup with tea pulls clean added after merge
3. Gitea skill already referenced via frontmatter (line 7)
The fixes are minimal, correct, and ready to merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Fixes two bugs in the code-reviewer agent discovered during spawn-issues orchestration:
tea commentcauses backgrounding and silent failureCloses #62
Changes
tea pulls clean <number>to step 5 after mergingTest Plan
AI Code Review
Summary
This PR correctly addresses both bugs in the code-reviewer agent: the heredoc syntax issue causing silent failures and the missing branch cleanup after merging PRs. The fixes are minimal, targeted, and complete.
Findings
Code Quality
Potential Bugs
Security Concerns
Style Notes
Test Coverage
Verdict
LGTM
All three acceptance criteria are met:
The fixes are minimal, correct, and ready to merge.