archlint: Enforcing Architecture Boundaries in CI, Deterministically
Architecture decisions stay true on the wiki and rot in the code. archlint enforces the boundaries in architecture.json on every commit, no model.
Tag
Version control with Git: branching strategy, rebase discipline and hunting bugs in production.
There are 8 posts with this tag.
Architecture decisions stay true on the wiki and rot in the code. archlint enforces the boundaries in architecture.json on every commit, no model.
I added a deterministic flaky-test filter to CommitBrief: it catches hard-coded sleeps and unseeded randomness at commit time, with no model.
Two new commands: summary briefs a change and its history, and remote pr reviews a PR from the terminal, leaving comments before the human does.
Not the 'why' but the 'how much': which workflow layers the tool plugs into, the bug patterns it keeps catching, and where it hits its limits.
One afternoon I hit the limits of self-review, so I wrote a tool that audits my own diff without leaving the terminal: CommitBrief.
From workflow selection to bug hunting with bisect, rebase discipline, worktrees, and signed commits — things I noticed after years of using Git.