📰 Dev.to · benjamin

GitHub Actions won't tell you your CI is getting worse. I built a zero-dep CLI that does.

The same root cause keeps coming back because nobody tracks it. I built a zero-dep CLI that does.

I kept finding gaps in my repos after open-sourcing — so I built a zero-dep CLI to catch them first

I kept shipping version mismatches — so I built a zero-dep CLI that checks all three sources at once

A reformatted PR shows 80 changed lines but changed nothing — I built a zero-dep diff that sees through it

Is that timestamp in seconds or milliseconds? I built a zero-dep CLI that just tells you — both directions.

Putting a file in .gitignore does nothing if git already tracks it. I built a CLI to find the leftovers.

Your git history is already your changelog — I built a zero-dep CLI to extract it

Your package.json diffs are noisy for no reason. I built a zero-dep fixer.

I committed a 200 MB file once. Never again — so I built a zero-dep pre-commit guard.

Two branches, the same migration number, one broken deploy. I built a zero-dep linter for that.

I built a zero-dep CLI that finds unused dependencies — and is wrong less often than depcheck

Every TODO in your codebase is lying about its age. So I built a CLI that blames them.

Your dev stack is 4 terminal tabs. It could be one labeled stream.

I built a local dead-man's-switch for cron jobs (no server, no signup)

I built a 1-file CLI to catch .env drift before it causes production bugs