commit-rewriter 0.2 adds a single feature: support for rewriting commits on non-default branches. It's a small upgrade, but the tool's very existence points to a workflow friction that's often overlooked.

What this is

commit-rewriter is a command-line tool written by independent developer Simon Willison, used to rewrite Git repository commit history—turning messy commit logs into something humans can actually read. Version 0.2 adds support for targeting non-default branches.

For people who don't write code, "rewriting commit history" is essentially the same as revising a document draft—erase the messy middle, leave a clean final version.

Industry view

Simon Willison is treated as a "tool artisan" in the English-speaking developer community, but let's be direct: this update does not qualify as an industry event.

The contrarian angle: is spending energy on "making commit history look pretty" putting the cart before the horse? What actually moves team efficiency is requirements management, code review, and test coverage—no matter how tidy your commits are, if the code itself is garbage, it's useless. Most teams haven't even sorted out their branching strategy yet; polishing history first is textbook premature optimization.

The other side: but as teams scale, when you run code review, compliance audits, or post-incident retrospectives, "clean, readable commit history" shifts from nice-to-have to must-have. This tool's evolution runs in the same vein as AI-generated commit messages—both tackle the same problem: code is written by humans, but it has to be readable by both machines and the humans who come after.

Impact on regular people

  • For enterprise IT: Worth letting engineering teams evaluate during code base migration, branch consolidation, or compliance audits. Non-technical departments will barely notice.
  • For individual careers: Limited impact. Unless you're a developer or manage a team of 5+ engineers, no need to pay attention.
  • For consumer markets: Essentially zero. A tool upgrade aimed squarely at developers.