Now
What shipped, and what we measured to decide it.
Engwire reached its first release on 2 September 2026, and this log starts around there rather than reaching back over everything built before it. What is here is not padding: an entry carries a shipped change, a measurement, or a method somebody else can run. One with none of those would not be written.
Subscribe by RSS →13 entries · no email, no account
A downgrade must not guess whether a review already happened
The schema is stamped and a newer one refused — and the one release that cannot be stopped is the one that shipped before the gate existed.
FixKonstantin Tarkus
Reviewing pull requests with Claude Code on your own machine
The sixteen lines that do it, and the seven things they get wrong — five you can fix, and two that are somebody else's software changing under you.
GuideKonstantin Tarkus
A starter config that cannot drift from its parser
Unknown keys are an error, which makes the generated file the documentation — so a test uncomments the whole thing and feeds it to the real parser.
FixKonstantin Tarkus
What an AI code reviewer can reach on your laptop
Six places a contributor's branch can reach when you run an agent on it, how far each one is actually closed — and the seventh, where the honest answer is nothing.
GuideKonstantin Tarkus
Whose launchd job is this? A default cannot say.
An installation is its data directory — so a resolver with sensible fallbacks has to be stopped from filling in an identity it does not have.
FixKonstantin Tarkus
Will Engwire review this pull request?
The decision has four stages and the order matters — a request can clear every rule and still wait, and queued work is re-judged against the config in force rather than the one that scheduled it.
GuideKonstantin Tarkus
Writing a Claude Code skill that reviews pull requests
Engwire ships no reviewer, so review policy is a Markdown file you own. Here is the contract it must keep, and the ways a skill silently does not run.
GuideKonstantin Tarkus
No skill is bundled. There is now one to install.
engwire-review posts one review, proves what it says against the code it was pinned to, and will not request changes on your behalf.
ReleaseKonstantin Tarkus
Two checks that passed when they should not have
A flag can survive its own removal, and a stray carriage return could turn a line nobody had measured into a value that looked fine. Both checks tested a proxy instead of the thing.
FixKonstantin Tarkus
Identity from issue events, not the timeline
A review request is an event, not a state — and on a busy pull request, reading it from the timeline carried sixteen times the payload to find it.
MeasuredKonstantin Tarkus
Engwire v0.1.0
The first release. It ships no reviewer, reviews nothing until you name a repository, and promotes no tag until every binary has run off the machine that built it.
ReleaseKonstantin Tarkus
What runs when git checks out code you have not read
Four ways a checkout runs a program, every one of them the reviewer's own config and one of them aimed by the branch — and the exposure starts at clone, before a tree exists. Measured on git 2.54, and closed down to one stated residual.
FixKonstantin Tarkus
What --setting-sources user actually stops Claude Code loading
Four things a contributor could commit, planted in a directory to see which of them one Claude Code flag actually stops — and why the check that it still works needs two probes, not one.
MeasuredKonstantin Tarkus
Where an entry claims something about Claude Code, git or GitHub, that was established by running it. The recipes are in the repository, next to the code they justify.
Read the experiments →