The Problem I Keep Running Into
I've written the same bash script scaffolding at least 40 times. Every time I spin up a new automation, I start from scratch: add the shebang, remember the set -euo pipefail line, define variables, write the same error-handling block I always use, forget to add a usage message until the third time I run it wrong.
And don't get me started on chmod. I Google "chmod 755 vs 644" at least once a month, even though I know what it means. The octal-to-permission mapping just doesn't stick unless you're using it every single day.
So I built something to fix both of those problems — and it's turning into a whole directory of tools.
What I Built: bashsnippets.xyz/tools
bashsnippets.xyz/tools is a free directory of interactive tools for Linux users and developers. No signup. No rate limits. Works in the browser. Copy and go.
Right now it has two tools live, with a new one shipping every week:
1. chmod Permissions Builder
Click checkboxes for read/write/execute across owner/group/others. Get the exact chmod command instantly — both octal and symbolic — with a plain-English explanation.
Example output:
chmod 755 filename
chmod u=rwx,g=rx,o=rx filename
Owner: read + write + execute
Group: read + execute
Others: read + execute
If you've ever second-guessed whether a script needs 755 or 744, this eliminates the lookup step permanently.
2. Bash Boilerplate Generator
Pick your script type (automation, backup, monitoring, deployment), toggle options (error handling, logging, dry-run mode, help message), optionally inject a snippet from the library, and get a production-ready .sh template with everything wired up.
No more blank files. No more copying the same header block from your last script.
→ Try the boilerplate generator
What's Coming Next
I'm shipping a new tool every week. The queue right now:
- Cron Job Builder — visual cron syntax builder with plain-English output
- Exit Code Lookup — paste an exit code, get the meaning instantly
- systemd Unit File Generator — build service files without memorizing the spec
Each one solves a specific "I always Google this" problem.
Why I Built This (and Why It's Free)
I got tired of opening 6 Stack Overflow tabs every time I needed to do something I'd done 20 times before. These aren't complex problems — they're just pattern-matching tasks where the syntax is annoying to remember.
The tools are free because:
- They're simple enough that paywalling them would be ridiculous
- I want them to be genuinely useful, not VC-funded SaaS bloat
- The snippet library (which the tools complement) has always been free
There's no business model. Just a side project that scratches an itch I have, and apparently a lot of other people have too based on the YouTube Shorts I've been posting.
Try It
If you spot bugs, missing features, or have ideas for new tools, drop a comment. I'm building this in public and genuinely want feedback from people who actually use bash day-to-day.
Top comments (0)