Finish and Export Review

Time: 6 minutes. Tangible win: choose the correct finishing path for the review.

Finishing is a separate skill from finding issues. `tuicr` lets you track progress inside the TUI, copy structured markdown, pipe output to another process, or submit a real review to a forge.

Primary source The tuicr README documents clipboard/stdout export and forge submission targets. GitHub's PR review reference explains Comment, Approve, and Request changes decisions.

Finish map

Situation	Action
You want to remember what you already inspected.	Use `r` for file reviewed or `R` for hunk reviewed.
You want to paste feedback into an agent.	Press `y` to copy structured markdown.
You want markdown in a file or script.	Run `tuicr --stdout`.
You want the review posted to the forge.	Run `:submit` and choose the review decision.

Useful stdout patterns

tuicr --stdout > review.md
tuicr --stdout | pbcopy

Agent handoff habit Before pasting exported comments into an agent, scan the markdown once. Make sure each comment still has enough file and line context to be actionable.

Retrieval check

You want a coding agent to address review comments before anything is posted publicly. Which finish path fits best?

Correct. Copy structured markdown with y and give it to the agent.

Not quite. Use y to copy structured markdown before asking an agent to act.

Practice

Name the review decision you would submit: comment, approve, or request changes.
Explain why that decision matches the comments you left.
Export the review to clipboard or stdout on a low-risk practice change.

Ask the agent to inspect exported review markdown and turn it into an implementation checklist.