If you use arch but you are forced to be on a mac for any reason, this will make you hate yourself less.

Wrapping these in a TUI is on my list. Haven't built it yet.

Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.

Sure, normalizing by size would be more precise. But this is a quick gut check to know which files to look at first, not a metric.

Fair point. I skip lockfiles, changelogs, and generated code. The first application file on the list is the one that matters. Should have been explicit about that in the post.

Only two of the five depend on commit messages. Churn, authorship, and velocity work regardless. Even teams with terrible hygiene write "fix" when something breaks.

As noted, authorship does not if commits are squashed, which seems to be common (I never do it).

> Even teams with terrible hygiene write "fix" when something breaks.

They might not include anything but the Jira ticket number, if the environment is truly lacking.

Big projects tend to self-correct. These commands hit differently on private codebases with 3-10 contributors, where high-churn usually means one person patching the same thing repeatedly.

Good catch, that's better

Very happy to hear!

Is this the same DPI device that snoops on DNS to shape bandwidth?

No. AFAIK it doesn't do any DPI. It's only for user messaging (content injection).