GiviLoop: keeping code review findings tied to the right MCP review run

I'm the author of GiviLoop, a free CLI and MCP tool with an MIT license. It lets a coding agent get a second opinion from a local model or web chat, then check the findings against the code and tests.

A useful detail from a recent Reddit discussion: if a new review starts, a later tool call should not quietly update the latest review. Finding writes now require an explicit runId. Updates use both runId and findingId, with no fallback to latest. This is covered in v0.8.2: https://github.com/vgflutter/GiviLoop/releases/tag/v0.8.2

The agent records each finding as confirmed, dismissed or unverified, with evidence. One documented Claude review found a real reporting bug but also flagged an error path that was already handled. Checking the actual CLI dismissed that second finding: https://github.com/vgflutter/GiviLoop/blob/main/docs/examples/double-check-report.md

The report stores the assessment; it does not prove the tests ran. Context is prepared from Git and files to avoid a long agent-written handoff. Local models or existing web chats can avoid a separate paid API review. Agent tokens and chat quotas still apply, and total savings are not measured.

Code and setup: https://github.com/vgflutter/GiviLoop

Written with help from ChatGPT using the linked project docs.