Skip to main content

Review code in VS Code

Goal: review your working tree's changes in VS Code, understand the findings, apply the fixes by reviewing each diff, and generate the commit message — without leaving the editor.

The Imaginne extension brings the agent into VS Code and routes every edit through a Proposed Changes area, so nothing touches disk without your approval. For the full picture, see Using VS Code.

Prerequisites​

  • The imaginne (CLI) binary installed and the Imaginne extension (nnumbers.imaginne) active. See Install VS Code.
  • Be signed in (the Imaginne: Login command or /login in the chat).
  • A Git repository open as a workspace, with changes to review.

Step by step​

1. Review the current changes​

You can trigger the review in two ways:

  • From the command palette: Imaginne: Review Current Changes.
  • From the Source Control (SCM) tab menu: the action to review the current changes.

The extension collects your diff and the agent analyzes the code.

Other review scopes

There are also Review Staged Changes, Review Branch vs Base, and Review File (in the explorer). Use the right scope for what you want to audit.

2. Read the findings​

The results appear in the Review panel, organized by severity. Each finding describes the problem and its location. Use the list to prioritize — start with the most serious items.

3. Apply fixes with /fix​

To fix something, ask the agent directly in the chat, referencing the problem:

/fix Fix the resource leak flagged in src/db/pool.ts:
the client isn't released when the query throws an exception.

For errors the editor itself already flags (diagnostic underlines), use the Fix with Imaginne lightbulb action over the diagnostic — it sends the /fix already carrying the error context.

4. Review and apply the diffs​

Every proposed edit enters Proposed Changes (Composer) before going to disk. There you decide:

  • Diff — see exactly what changes in each file.
  • Apply / Reject — per file; or Apply All / Discard All for everything.
  • Hunks — apply or reject hunk by hunk, if you want to accept only part.

If a file changed since the proposal, the conflict guard warns you (a conflict badge) so you can reassess before applying.

Permissions and limits

Depending on the autonomy level (Ask / Fix / Agent / Bypass), the agent may ask for confirmation per file or per command. Writing outside the workspace always confirms, and destructive commands never run automatically. See Autonomy & permissions.

5. Generate the commit message​

With the fixes applied, generate the message:

  • The Imaginne: Generate Commit Message command, or the same action in the SCM menu.
  • In the Review panel, use Copy & fill SCM to paste the message straight into the commit box.

Review the text and commit normally through Git.

Result​

Reviewed changes, applied fixes (each diff approved by you), and a commit message ready in the SCM box. Because everything went through the Composer, the working tree reflects only what you accepted.

See also​

Using VS Code

Chat, Proposed Changes, the Review and Tests panels, and the autonomy modes.

Open →Autonomy & permissions

Ask/Fix/Agent/Bypass and the limits that always apply.

Open →Install VS Code

Extension, CLI, and settings.

Open →