fix(skills): prevent premature thread resolution on self-authored PRs

[worktrunk-bot]

Summary

• Adds thread-resolution guidance to review-pr skill Step 6 requiring substantive verification before resolving threads (not just checking if the author rewrote the code)
• Adds specific warning about self-authored PR bias where the bot is both author and reviewer

Evidence

Run 23182191893 reviewing PR #1583 (fix/issue-1572-trash-dir):

The bot's earlier review correctly identified that linked worktrees can live on different mount points, so rename() from a linked worktree path to .git/wt-trash/ could fail with EXDEV. It suggested a doc comment:

For the main worktree, .git/ is on the same filesystem, so rename() is an instant metadata operation. Linked worktrees on different mount points will get EXDEV and fall back to legacy removal.

In run 23182191893 (incremental review), the bot encountered the author's version which claims "The .git/ directory is always on the same filesystem as the worktree (git requires this)" and reasoned "The author's version is actually more accurate." It then resolved the thread.

The original suggestion was correct — git does NOT require .git/ and linked worktrees to share a filesystem. The .git entry in a linked worktree is a file pointing to <git-common-dir>/worktrees/<name>, and that common dir can be on any mount point. The code handles this correctly (fallback to legacy removal on rename failure), but the doc comment is misleading.

Root cause: When the bot authored the PR and then reviews it, there's a bias toward trusting the code's own claims rather than independently verifying them.

Other observations (no action needed)

• Inconsistent skill loading: Run 23182191893 skipped loading running-in-ci, unlike all other review sessions. Intermittent model behavior, not fixable via skill changes.
• Verbose subagent on mention: Run 23181353198 spawned an Explore subagent with 19+ tool calls for a straightforward documentation question on issue Hook names and order are not clear #1571.
• Overlapping responses: Two bot comments on issue Hook names and order are not clear #1571 (runs 23181353198 and 23182166432) partly overlap in content. Structural limitation from multiple triggers on the same thread.

Sessions analyzed

Run	Workflow	Branch/Trigger	Conclusion
23182731689	claude-review	fix/issue-1572-trash-dir	Clean
23182468426	claude-review	nightly/clean-23181835484	Clean
23182191893	claude-review	fix/issue-1572-trash-dir	Thread resolution error
23182037455	claude-review	fix/copy-ignored-post-create-example	Clean
23182671268	claude-mention	issue_comment	Clean (silent exit)
23182274999	claude-mention	issue_comment	Clean (silent exit)
23182166432	claude-mention	issue_comment	Clean
23181624794	claude-mention	issue_comment	Clean (silent exit)
23181510462	claude-mention	issue_comment	Clean (silent exit)
23181353198	claude-mention	issue_comment	Verbose but correct
23181459573	claude-issue-triage	issue #1578	Clean

🤖 Generated with Claude Code