Muhammet Şafak
Author and maintainer of CommitBrief
Muhammet Şafak writes and maintains CommitBrief, the local-first CLI that runs LLM code review on git diffs, and archlint, the static architecture linter whose config CommitBrief reads to review a change against a repo's declared layers. His posts here cover the problems that work runs into rather than the product: getting structured output back from models that disagree on how to produce it, gating CI on review findings without drowning a pull request in comments, and the trade-offs of keeping the whole pipeline on the developer's machine.
9 posts
Proving the review happened: SOC2, audit chains, and the compliance angle of `--json`.
What auditors actually ask when they say 'every commit was reviewed,' and how CommitBrief's JSON output and cache-key design fit into an audit chain — without overpromising what an LLM review can be evidence of.
The cost of a junior waiting for a senior, and what an LLM can — and can't — do about it.
A junior's 30-minute change ties up six hours of a senior's time. The LLM isn't a mentor, but it can be the assistant that frees senior time for actual mentorship.
Where your AI reviewer runs matters.
CodeRabbit, Greptile, Copilot review, and Bugbot compared with a local CLI: where each runs, who holds the key, what leaves your machine.
Cross-timezone review lag, and turning the reviewer from blocker into validator.
The hidden tax on async teams: a junior's PR waits for a reviewer who's asleep, then for one who's in a meeting. An LLM in the middle of that chain doesn't replace anyone — it changes what waiting means.
The solo developer's missing second pair of eyes.
For OSS maintainers, indie hackers, side-project builders — there's no one to review your code. What an LLM fills in, and what it deliberately doesn't.
Three flags into one subcommand: the `commitbrief diff` collapse and what it taught me about CLI surface area.
v0.9.0 retired --commit, --branch, and --pull-request in favour of a single 'diff' subcommand that pass-throughs to git diff. A note on why reinventing what git already does is the wrong shape.
v1.0 is an API freeze: what `schema: v1` actually promises.
v1.0 isn't just a number. CLI flag surface, JSON schema v1, and the COMMITBRIEF.md / OUTPUT.md formats are under strict semver from here on. Here's what that buys you, and what it stops me from doing.
Why a CLI, not a GitHub App.
On trigger ownership when picking a code review tool. The design thinking behind CommitBrief as a CLI — and when that's the wrong choice.
LLM code review doesn't replace human review. It multiplies it.
The position paper that ships with v1.0 — what an LLM catches, what it doesn't, and why a human reviewer's job changes shape rather than disappearing.