explaingit

finallyblueskies/sdrev

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 2/5Setup · easy

TLDR

A command line tool that turns a Git diff into a browser-based code review, using an AI model to describe each changed section in plain language.

Mindmap

mindmap
  root((sdrev))
    What it does
      Semantic code review
      HTML report
      AI diff descriptions
    Tech stack
      TypeScript
      Bun
      Git
    Use cases
      Review a branch diff
      Compare two commits
      Review AI generated changes
    Audience
      Developers
      Code reviewers
      Claude Code users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Generate a browsable HTML code review from a Git branch comparison

USE CASE 2

Get plain language descriptions of what changed in each part of a diff

USE CASE 3

Compare two commits or branches directly by name from the command line

USE CASE 4

Review your own AI coding assistant's changes before merging them

What is it built with?

TypeScriptBunGit

How does it compare?

finallyblueskies/sdrev0xkinno/astraea0xkinno/halcyon
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasyhardhard
Complexity2/54/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Best used with an already authenticated Codex or Claude Code session, though a direct OpenAI or Anthropic API key also works.

In plain English

sdrev is a command line tool that turns a plain Git comparison, like the changes on a branch versus main, into a code review you can browse in your web browser. Instead of just showing you raw lines added and removed, it builds a structured diff of what changed and then asks an AI language model to describe each changed section in plain language, so you get a written explanation sitting right alongside the highlighted code. Everything ends up in one self-contained HTML report you can open and click through. It installs as a single standalone program, so you do not need Node.js or Bun to run it, only Git itself and a short install script that downloads the right binary for macOS or Linux. Once installed, you simply describe what you want compared in plain English, such as comparing the last few changes related to a certain feature, and sdrev works out which commits that refers to using an AI coding assistant session you already have set up, either Codex or Claude Code. You can also skip that step and directly name two Git references to compare. By default sdrev tries to use Codex to figure out what you meant and to write the descriptions, and it falls back to Claude Code if Codex is not available, using a smaller and larger model for the two different steps. You can override which provider and model it uses, or plug in your own OpenAI-compatible or Anthropic API key and model name directly. Reports are saved locally under a hidden folder inside your repository, organized by which two commits were compared, and the viewer remembers things like which files you had already looked at and where you had scrolled to. The project also ships a Codex skill and a Claude Code slash command that call the same underlying tool, and building it yourself requires the Bun runtime.

Copy-paste prompts

Prompt 1
Install sdrev and show me how to compare my current branch with main
Prompt 2
Explain how sdrev picks between Codex and Claude Code to describe a diff
Prompt 3
How do I use sdrev with my own OpenAI or Anthropic API key instead of Codex?
Prompt 4
Set up the Claude Code /sdrev command in my repository

Frequently asked questions

What is sdrev?

A command line tool that turns a Git diff into a browser-based code review, using an AI model to describe each changed section in plain language.

What language is sdrev written in?

Mainly TypeScript. The stack also includes TypeScript, Bun, Git.

How hard is sdrev to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is sdrev for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.