GitGlow logoGitGlow
Download
GitGlow 2.0.3 guide

Review confidence and verification

See which files you reviewed and whether checks still describe the current code.

Reviewed for 2.0.3Updated September 20, 2026
On this page

What this helps you do

See which files you reviewed and whether checks still describe the current code.

Find it in GitGlow

Choose Review confidence below the repository workbench, from a managed run, or from Release.

Before you start

Pro. Commands run locally only after you choose Run verification. AI provider usage is separate.

Steps

  1. Choose a comparison base, or leave HEAD for current working changes. Inspect each text diff and mark it reviewed.
  2. Enter a verification command and timeout. Run it, inspect output, or cancel while it is running.
  3. Edit or stage a file to see review marks change. A later checkout edit makes the previous verification stale; run the checks again.

Expected result

Review marks are bound to the diff and comparison base. Verification records the tracked and nonignored untracked checkout content, index, HEAD, and branch. Passing is evidence for that code state, not proof of correctness.

Controls

Mark reviewed / Mark unreviewedreview.mark

Binds the reviewed mark to the currently displayed diff; subsequent edits invalidate it.

Screen
Review confidence
Available
Pro
Open workflow guide
Run verification / Cancel verificationreview.verify

Runs the chosen command with a timeout and marks results stale when checkout content changes.

Screen
Review confidence
Available
Pro; cancellation remains available
Open workflow guide

Recovery

If the workflow cannot continue

Sensitive, binary, symlink, submodule, and oversized files require external inspection. Incomplete fingerprints cannot show verification as current. No detected test command means no checks configured; git status is never treated as a test.