A snippet that fails on your distro, a tool that returns the wrong hash, a gap in the free library you keep hitting in production — that is what this page is for. Vague "it broke" messages without context sit in the queue behind reports that include enough detail to reproduce the failure.
Pick the channel that matches what you need. Email is the only route for bug fixes, script requests, and questions about the Production Bash Toolkit purchase.
Without these four details, a bug report turns into a back-and-forth thread that burns days. Include your OS and version (e.g. Ubuntu 22.04, Debian 12, macOS 14 with Homebrew bash), what you already tried and the exact command or cron line you ran, the full error output or unexpected behavior — paste stderr, not a paraphrase — and whether the issue is about a free snippet, an interactive tool, or the Production Bash Toolkit download. Screenshots of terminal output are fine; "it crashed" is not.
BashSnippets is a one-person project maintained alongside production sysadmin work. Email gets a response usually within 2 business days. Reproducible bug reports with version info often get a same-week fix pushed to the site. Script requests are triaged by how many operators would hit the same failure — niche edge cases may not get a dedicated page. YouTube and dev.to comments are read, but email remains the channel for anything that needs a code change or a direct answer about your environment.
Can I request a specific bash script?
Yes. Send the use case — what breaks without the script, what OS and shell version you run, and any constraints (cron-only, no root, must work on macOS). Requests that match problems other sysadmins hit get priority. There is no guarantee every request becomes a published snippet, but actionable, consequence-first requests land on the backlog.
Do you offer custom automation work?
BashSnippets.xyz is a free library and toolkit publisher, not a consulting shop. Custom automation, on-call retainers, and paid script development are not offered. For one-off questions about adapting a snippet to your environment, email with your OS, what you tried, and the exact error — that is in scope.
How do I report a bug in a snippet?
Email anguisheh1@gmail.com with the snippet slug or URL, your OS and bash version (output of bash --version), the command you ran, and the full stderr or unexpected behavior. A minimal reproduction — the smallest script that still fails — gets a fix faster than a vague "it does not work" report.