Review pull requests with ease using Flight Plan.

An offline-first code review tool that helps you understand and navigate the changes in a pull request. See what changed, how it runs and what it can break before you read the diff, built on your machine with no model. When you want the why, your coding agent explains each part and flags potential bugs.

$npx @kidlat-dakila/flightplan@latest

Or try our demo to see it first-hand!

Flight Plan's review page for pull request 57 of pokedex-web, at the Change Overview: the changed code blocks in rows by the kind of code they are, Page, Component, Schema / data model, UI state and Logic, between the tree of changed files and the Sections rail.

Take in the whole change first.

Every changed code block, sorted by the kind of code it is.

Spot the new page, the components it renders and the state behind them before you open a file. The Change Overview puts each changed code block in a row with others of its kind and marks it added, modified or deleted. Flight Plan builds it from the code with no agent, and a card with a waypoint takes you straight to its code.

The Change Overview of the Pokemon page review, with its changed code blocks in rows by classification, Page, Component, Schema / data model, UI state and Logic. The pointer rests on the card of usePokemon, which shows the hook's code.

See how the change runs.

From the first trigger to the changed line, on one board.

Follow the behaviour without jumping between files. Flight Plan draws the path from the syntax trees, from what starts the code through each function it passes to the line you changed, and tags each card with the kind of code it is. Your agent can label each step in plain words.

A Trace Diagram in full screen, from a FastAPI review. The side panel shows the code of create_pokemon() with the waypoint for its session.commit() open, beside the route handler add_pokemon that calls it.

Find what breaks before you merge.

The blast radius, including files the diff never shows.

Catch trouble in code the pull request never touched while you are still reviewing it. Flight Plan maps every file the change reaches through its imports, and your agent can check each one for what breaks or behaves differently.

A Blast Diagram in full screen, in its Import bound view: the changed files of the pull request among the files they import that the change did not touch, such as SessionProvider.tsx and button.tsx.

See the risk on the line that causes it.

Each part of the change explained, risks included.

Know where to slow down before you start reading. Flight Plan marks each changed block of code as a waypoint, and your agent explains what it adds or changes, right above its lines. When it finds a risk, it says what could happen, traces how it gets there and shows you the fix.

A waypoint of the Code Walkthrough marked Risk: PokemonFilters hides a failed load of the trainers, with the trace of how it happens and the suggested fix as a diff.

Start with the code you care about.

Your topics and the core of the change, marked on the waypoints.

See at a glance which parts of a change touch what matters to you. Pick your topics in setup, such as API requests or security, and Flight Plan marks every waypoint and code block that touches one with Spotlight. Your agent marks the core changes, the parts the branch is built around, and says why. Pick the Most important first order and the walkthrough starts with them.

A waypoint for the hook usePokemon(), marked Core change and Spotlight. The agent explains what the hook does, then why the rest of the change depends on it.

Read only the parts you came for.

The walkthrough, narrowed to the waypoints you want to check.

Go straight to the components and the UI state, or to the code your agent flagged. Flight Plan sorts every waypoint by the kind of code it changes and by whether that code was added, modified or removed. Pick what you want and the walkthrough hides the rest.

The Code Walkthrough filtered to Component and UI state. The filter has gone to the first waypoint it keeps, the Zustand store usePokemonFilters, and shows its card above the code.

Look up any name without leaving the diff.

Where each name in the code is defined, and where it is used.

Follow the code without opening another tab. Hover a name and Flight Plan shows where it comes from. An exported function lists the files that use it, and a variable shows the line that defines it.

A hover card on usePokemonFilters in the code. It lists 2 usages in 2 files, the lines of use-pokemon.ts and PokemonFilters.tsx that call it.

Ask for the why when you need it.

Your agent explains the parts you pick, when you pick them.

Spend your agent's time on the code you want explained. Every review opens already built, with short hints from Flight Plan on the parts nobody has explained yet, such as "Adds a component." Press G and your agent explains that line and checks it for issues, or press Ctrl+G for its whole code block. To have it explain the whole review, pick Explain this review in the ⚙ menu and choose the parts it writes.

The dialog that asks Claude to explain a review. It lists the parts to explain, the prompt configuration, the Code Walkthrough order, the segments and the 29 waypoints to check, above the buttons Configure, Not now and Explain.

Explanations written your way.

Pick a preset, or tune every prompt yourself.

Don't like how your agent writes? No problem. Get short notes, or explanations for someone new to the code. Every part your agent writes has its own prompt, from the overall writing style down to how a single waypoint is worded, and you can rewrite any of them. Start from one of the four presets that ship with Flight Plan and duplicate it to make it yours.

Flight Plan's settings for the Standard configuration: a list of every field of a review at the left, and the instruction for how the agent writes a waypoint's reading, open in an editor.

Questions? We've got answers.

Does my code leave my machine?

Flight Plan keeps every review in ~/.flightplan and writes nothing into your repositories. It sends data in two cases only: to your forge when you comment or submit a review, and to a Claude artifact when you publish one. The coding agent you connect keeps working the way it always does.

Do I need a coding agent?

Not to read a review. Flight Plan builds it from the code with no model, including the segments, the diagrams, the Change Overview and the files and lines of the walkthrough. What it can't do alone is explain each part of the change and find potential bugs. That's what your agent adds. Setup asks you to pick one, and Flight Plan calls on it only when you ask it to explain.

Which coding agents does it work with?

Claude Code, Codex and Cursor. Flight Plan installs its review skill and MCP server for each one you pick. It can start Claude Code for you, and with any other agent you paste the prompt it gives you.

Is it token-expensive?

Flight Plan builds the whole review before your agent starts, including the segments, the diagrams with their nodes and edges, the Change Overview and the files and lines of the walkthrough. It does that by parsing your code into abstract syntax trees (ASTs) with tree-sitter, on your machine, and calls no model itself. Your agent only writes the text and the findings, and only for the parts you pick. Ask it about one line or one code block and it writes just that. It spends no tokens on the structure or on tracing who calls what, because the ASTs already show which functions call which. When Flight Plan starts Claude Code, it runs as an interactive session on your subscription.

Where do my pull requests need to live?

Anywhere git can reach them. By default Flight Plan reads the branches in your checkout with plain git, with no token and no network. Connect GitHub, GitLab or Bitbucket, including GitHub Enterprise, self-managed GitLab and Bitbucket Data Center, to review their pull requests, comment and submit reviews.

Which languages does it understand?

TypeScript, JavaScript and JSX, Python and Vue.

Can my agent leave part of the change out?

No. Flight Plan works out which files, lines and callers a review covers from the code itself, and the agent only writes the prose. The Code Walkthrough also says how many changed files it covers.

Do I need a pull request to use it?

No. You can review any branch, including your own work before you open a pull request. When the branch gets a pull request, its Flight Plan moves there.

Can I share a review?

Yes. Put it in the pull request description, or have your agent publish it as a Claude artifact. That's one page with the whole review and the code it shows, which anyone can read without installing Flight Plan.

How is it licensed?

Under the Functional Source License (FSL-1.1-ALv2). You can use, change and share it for any purpose except offering a competing commercial product or service. Two years after each release, that version is also available under Apache 2.0.

Your next review, on your machine.

Flight Plan reads TypeScript, JavaScript, Python and Vue, from local git or from GitHub, GitLab and Bitbucket. Add Claude Code, Codex or Cursor when you want each change explained and checked for bugs. It needs Node.js 22 or later.

~/.flightplan: Every review and every setting lives in this one directory on your machine.
Nothing in your repository: Flight Plan never writes into the code you review.
Sent only when you say: Comments go to your forge when you submit them, and a Flight Plan leaves your machine only when you publish it.

$npx @kidlat-dakila/flightplan@latest