CrossCheck Deck Mode
Turn a sprawling GitHub pull request into a guided review deck: briefing, risk map, review path, and publishable author feedback.
14-day Pro trial. No credit card required.
From PR sprawl to reviewer path
Deck Mode turns file lists into a sequence your brain can follow.
Reviewers do not need another wall of AI prose. They need a route through the change, with the risky decisions surfaced at the moment they are looking at the code.
The raw PR
Touches invoice state and webhook retry flow.
Copies a new plan matrix into the admin app.
Renames a helper used by review tools.
Creates the usage ledger table.
Adds coverage, but only for the happy path.
Documents the new pricing behavior.
The deck path
- 01
Read the migration first
Schema commits the product decision.
- 02
Trace webhook retries
This is where duplicate charges can appear.
- 03
Check statement failures
One rule already flagged missing rollback coverage.
- 04
Publish two questions
Ask the author before blocking the whole PR.
Pick the review depth
One PR can be a skim, a guided pass, or a full safety review.
Deck Mode starts with the same briefing, then expands the path based on how much human attention the change deserves.
The deck orders the important modules, annotates the risky pieces, and keeps you in reviewer mode.
Feature work, refactors, AI-generated medium PRs.
Review the ledger write before the UI copy. It is the only irreversible path in this PR.
What the deck builds
A review artifact, not another bot comment.
Each stage is durable and resumable. A reviewer can wait for the briefing, pick a mode, chat about unfamiliar code, then generate the plan without starting over.
Briefing
The PR becomes a story: what changed, why it matters, and how much review it probably needs.
Code modules
Related files are grouped by behavior instead of alphabetical order, so reviewers see the system shape first.
Risk map
The deck points at migrations, auth paths, data loss risks, missing tests, and statement failures.
Review plan
A file-by-file path tells the reviewer where to start, what to skim, and what deserves line-level attention.
Author feedback
Questions and suggested comments stay in a cart until the reviewer explicitly publishes them to GitHub.
Human in control
Suggestions stay in the cart until the reviewer sends them.
Deck Mode can draft questions and comments, but publishing is explicit. The reviewer owns the final signal that lands on GitHub.
Suggested feedback
Rollback path is not covered
This creates the ledger table, but the down migration drops it without preserving unbilled rows.
Retry idempotency needs a key
The webhook handler retries after timeout, but the write does not appear keyed by provider event id.
Copy looks good
The UI change is isolated. I would skim this after the billing path.
Published to GitHub
This creates the ledger table, but the down migration drops it without preserving unbilled rows.
The webhook handler retries after timeout, but the write does not appear keyed by provider event id.
Details
Built for real review workflows.
Is Deck Mode replacing statement checks?
No. Statements still produce pass/fail evidence on the PR. Deck Mode is the human review surface for the PRs that need orientation, judgment, or follow-up.
Can reviewers publish the AI's comments automatically?
No. Suggested questions and comments stay selected locally until a reviewer chooses to publish them. Deck Lab runs cannot publish at all.
Where does the deck live?
Inside the PR surface in CrossCheck. The PR shell keeps Description, Files, and Runs, with Deck Mode opening as a full-screen walkthrough.
How do teams try it?
Start the 14-day Pro trial, install the GitHub App, and run CrossCheck on a real pull request. No credit card is required.
Give every big PR a review path.
Install CrossCheck, run it on a real pull request, and open the deck when the change needs a human.
14-day Pro trial. No card. No CI step. No model keys to manage.