Posting Review Summary

Context Detection

Check contexts in this order — use the first match:

Context	How to Detect	Action
Local output in effect	An `OUTPUT: local files` line in the prompt's leading directive block, or a caller that passes local files as the destination in effect. Check this first, and never key it on which tools happen to be available	Write to the summary path the caller passed. With no path, pick none: return the formatted summary in your reply and say no destination was given. `bitwarden-code-reviewer` resolves the directory and file name in its Step 1 and passes it on every invocation; this skill never picks either
Local target, no GitHub destination	The review target is local changes and no caller declared a GitHub destination	Write to the summary path the caller passed. With no path, pick none: return the formatted summary in your reply and say no destination was given
Agent Mode	Sticky comment context provided in prompt (comment ID + `<!-- bitwarden-code-review -->` marker)	Write summary to `/tmp/review-summary.md`
GitHub Actions (tag mode)	`mcp__github_comment__update_claude_comment` available AND no sticky comment context	Update sticky comment via MCP tool
Local review	Neither agent mode context nor MCP tool available	Write to the summary path the caller passed. With no path, pick none: return the formatted summary in your reply and say no destination was given

FORBIDDEN: Do not use gh pr comment to create summary comments.

If PR title, description, or test plan is genuinely deficient, add as a finding in the Code Review Details collapsible section.