Add answer-feedback workflow to screenote skill#4
Conversation
Update SKILL.md Step 6 to instruct Claude to post an explanatory reply comment (via add_annotation_comment) before resolving each annotation, so reviewers know what was fixed or why feedback was declined. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PR SummaryLow Risk Overview Adds a new Written by Cursor Bugbot for commit c1e708d. This will update automatically on new commits. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
|
|
||
| The feature spans two repos: | ||
| - **claude-screenote** (this repo) — SKILL.md changes for comment-before-resolve behavior | ||
| - **screenote** (Rails app at `/home/asterio/Dev/screenote/`) — new column, mailer, and background job for digest notifications |
There was a problem hiding this comment.
| rescue => e | ||
| Rails.logger.error("Digest notification failed for user #{recipient.id}: #{e.message}") | ||
| # Comments keep notified_at as NULL; next job run will retry | ||
| end |
There was a problem hiding this comment.
Rescue scope causes duplicate emails on update failure
Low Severity
In the proposed send_digest method, the rescue block covers both deliver_now and update_all. If the email is successfully delivered but the update_all call then raises, the rescue fires, notified_at stays NULL, and the next job run re-sends the same digest. The edge case table claims "unsent comments" are retried, but this scenario involves already-sent emails being duplicated.


Summary
add_annotation_comment) before resolving each annotationadd_annotation_commentfails, Claude warns the developer and proceeds with resolution anywayTest plan
/screenote feedbackand verify Claude posts reply comments before resolvingadd_annotation_comment,resolve_annotation) already tested in screenote repo🤖 Generated with Claude Code