ShellDef

Beyond flagging problems, ShellDef rewrites the script and returns a corrected version. The fixes cover known issues in the scan, so you get a file that's closer to safe without editing every line by hand. It's the feature that separates it from a plain linter.

The scanner calls out commands that can wreck a system or leak data, like forced recursive deletes, disk formatting, or piping a remote download straight into a shell. Each one comes with a risk note so you can judge whether it belongs in your script at all.

Every finding gets a severity level, from low to critical. That ordering matters when a script has dozens of notes and you only have time for the top few. You fix the critical items first and leave the cosmetic warnings for later.

Each flagged line carries an explanation of what's wrong and why it matters. That turns a scan into a short lesson, which helps if you're still learning shell quirks or handed a script full of patterns you haven't seen.

You can drop a .sh file or paste raw code. Both paths feed the same analyzer, so a quick snippet check and a full-file audit take the same effort. This makes it easy to check something before you even save it to a file.

Once the scan finishes, you can download the corrected .sh file for immediate use. That saves the round trip of copying fixes out of a report and back into your editor.

ShellDef keeps a record of past scans. You can revisit an older report, compare what changed, or pull up the details on a script you reviewed weeks ago. Useful when you're tracking a fix across several iterations.