Command Menu

Search pages, blogs, projects, and more...

december 25, 20253 min read

Auto Copilot Review: Outsourcing My Insecurities to an LLM on Every Git Add

Because hitting `git commit -m "fix maybe?"` requires too much confidence in my own code.

Dev StoryProjectsVS CodeAIExtension

Auto Copilot Review: Your Code Is Bad and an AI Knows It

Writing code is easy. Reviewing your own code is functionally impossible because you already convinced yourself it was fine an hour ago.

You know that moment. Cursor hovering over the commit button. The cold creep of dread. Did you leave a console.log("here") in? Did you break a type in a file you only vaguely remember touching? Did you rename that variable to something embarrassing?

You have two options:

  1. Scroll through the diff, lie to yourself, and push to master.
  2. Manually open Copilot Chat, paste the diff, ask it to review, wait, context-switch back, forget what you were doing.

Option 1 leads to PR comments that age poorly. Option 2 is a full flow-killing chore that requires so much ceremony you never actually do it.

What if the AI just... watched?

Making Staging Aggressively Judgemental

I built a VS Code extension that hooks into the Git API. Every time you stage a file — git add, the little + button, however you do it — Auto Copilot Review wakes up, grabs the diff of everything staged, and fires it straight into GitHub Copilot Chat with a review request.

Zero clicks. Zero context-switching. You stage a file, you glance right, and there's already a breakdown of your logic problems waiting for you like a very patient disappointed parent.

It happens entirely in the background. The extension doesn't ask. It doesn't warn you. It just starts judging.

The "God, Slow Down" Problem

My first build was too eager. Embarrassingly eager.

I stage files by rapidly clicking + on five different files in a row, which in V1 meant five simultaneous Copilot API requests firing within one second. The Chat panel had a complete breakdown — five competing reviews flashing at once, each overwriting the last. It looked like a merge conflict with extra steps.

Turns out teaching a machine to review your code also means teaching it patience.

I added a configurable debounce timer — default 5 seconds. Now you can stage as frantically as you want. Once you stop moving for 5 seconds, everything gets bundled into a single review request. One clean response. No chaos.

It's a small thing. It's the thing that made it actually usable.

The Part Where It Actually Works

Within seconds of staging: a clean breakdown of your logic flaws, typos, forgotten debug statements, and edge cases you were hoping nobody would notice.

It feels like having an extremely pedantic code reviewer permanently installed on your shoulder, waiting for exactly the moment you're about to commit something embarrassing so they can quietly intervene.

The best part is it requires genuinely nothing from you after install. No commands. No shortcuts. No workflow changes. It just exists, watching, reviewing, and silently saving you from the PR comments that would have aged very badly.

Is it humbling? Yes. Does it catch things you'd have shipped? Also yes.

If you have a Copilot subscription and a realistic assessment of your late-night coding judgment, install the extension. Your future self — the one reading PR comments — will thank you.