Add CLI-Based Review Output

[lovestaco]

It would be very useful if the tool supported a CLI-first workflow for code reviews instead of relying on a locally served UI.

Proposed behavior

• Run a command like:

  git lrc review -t
  

• Output a formatted review directly in the terminal

Why this helps

• Works well in remote/dev environments like cloud workspaces or codespaces where running local UIs is inconvenient
• Faster feedback loop without switching to a browser
• Easier integration into existing workflows (e.g., scripts, CI)
• Better fit for developers who prefer terminal-based tools

The UI can still exist, but having a fully usable CLI output would make the tool much more flexible.

[lovestaco]

If it's a good idea, I can design how we can show output etc in terminal in the discussion.

Later can convert to issue if anybody wants to pick it up.

[shrsv]

The first thing I recommend nailing down is the higher level requirements in this. What are we optimizing for?

1. Interactivite TUI or non-interactive well-formatted markdown output?
2. Implementation complexity/speed
   2.1. Many "diff TUI" exist - but does any diff with discussion/comments thing exist for the TUI already?
   2.2. Can some form of TUI markdown viewer work (with syntax highlighting maybe) to start with?
3. Maintainability: As things change in either the API or the web ui -- this also has to keep pace, it is an extra layer (liability). On the plus side -- maybe it can be used for better automated tests etc (asset). My hunch is -- keep things minimal and simple to start with
4. Usability: What is the typical workflow in these? Do you copy issues and then paste it into a CLI agent? How do we support the "next step"?

[lovestaco]

Got it

[shrsv]

From the markdown TUI renderer side, there's glow: https://github.com/charmbracelet/glow. Maybe other options as well.