Easily Find Bugs In Shell Scripts With ShellCheck

Brief: ShellCheck is a handy utility tool that warns you of possible syntax and simple logical errors, without executing. You can also use it with Atom text editor.

As we all know, the terminal is an inseparable part of the Linux system. And behind everything we do in the terminal, there is the shell — a program that interacts with the operating system itself. Every command we enter in the terminal is ultimately interpreted by the shell and then it acts accordingly.

ShellCheck command line tool

Shell as a Programming Language

There is more to shell though. A UNIX shell is not a command interpreter only, it serves as a programming language too! Shell as a programming language provides variables, flow control constructs, quoting and functions.

A file containing shell commands and codes is called Shell Script. So, you can accomplish various complex tasks and automation for you system using shell scripts.

Anyway, as we are humans, we make mistakes. So obviously, while writing shell scripts you will make mistakes too, such as – syntactical errors, typos, bad patterns etc. Here, we are going to know about the tool — ShellCheck — that will help us with that.


ShellCheck is a static analysis tool for you shell scripts. It is open-source and developed mainly for Bash or sh scripts. Now you might wonder, what the heck is Static Analysis? Well, static analysis is a method for debugging a program by examining its (static) codes rather than running/executing it.

Let’s take a look at what types of things ShellCheck checks for:

  • Quoting: Shell has specific ways for using variables and strings. If you’ve used them incorrectly ShellCheck will warn you.
  • Conditionals: It will check for incorrect uses of test statements.
  • Frequently Misused Commands: ShellCheck will warn you about incorrectly used shell commands.
  • Common Beginner’s Mistakes: Various syntax errors that beginner Shell users make as Shell uses various strict syntax rules that differ from other programming languages. For example: you can’t put spaces around the = sign while declaring variables. Most languages wouldn’t care but here it matters.
  • Style: ShellCheck will provide suggestions for improving your code’s style.
  • Data & Typing errors: Various issues related to data and typing.
  • Robustness, Portability & Others: ShellCheck will give suggestions for making your scripts robust, warn you about portability issues with different shells (bash,sh,ksh,dash etc.) and various other things.

For documentation and various useful information, do not forget to check the ShellCheck GitHub Project:

ShellCheck on GitHub

Installing ShellCheck

For offline usage, you can install ShellCheck package on your system. On Ubuntu, enter the following command in your terminal:

sudo apt install shellcheck

For other distributions, check the GitHub ReadMe Installing section.

If you use Atom text editor, you can also use ShellCheck within you editor window on-the-fly. Just install the necessary atom packages for ShellCheck:

apm install linter linter-shellcheck

ShellCheck supports other editors, such as – Vim, Emacs, Sublime etc., as well. You can find a complete list on the GitHub ReadMe section.

Using ShellCheck


You can use ShellCheck online without installing anything on your system (you will need a web browser though, haha!).

  • Copy your shell script’s codes.
  • Visit the ShellCheck website.
  • Paste your codes in the editor.
  • It will show the ShellCheck output.

Here’s an example:

Using ShellCheck Online
Using ShellCheck Online

Command-line interface

After installing the necessary packages for ShellCheck on your system, you can use it from your terminal without any net connectivity. Just type the following command:

shellcheck <filename>

Replace the <filename> part with the filename of your shell script.

ShellCheck Command-line interface
ShellCheck Command-line interface

Editor Extensions

After installing necessary extensions for your text editor, you can see the ShellCheck output on-the-fly, without running the shellcheck command manually. Here’s how it looks on the Atom editor:

Atom with Linter-ShellCheck
Atom with Linter-ShellCheck

Pros & Cons

Whether you are a seasoned Shell programmer or just a beginner, you have everything to gain and nothing to lose by using ShellCheck. Whenever you are writing shell scripts, check it with ShellCheck, you will be able to catch errors and bugs early and overall be more productive with Linux.

Have you ever tried to write a shell script before? Did you use ShellCheck? If you did, how was your experience? Do share with us! :)

0 (0)
Article Rating (No Votes)
Rate this article
There are no attachments for this article.
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
List usernames instead of uids with the ps command for long usernames
Viewed 807 times since Wed, Jul 25, 2018
logrotate Understanding logrotate utility
Viewed 600 times since Sun, Jan 12, 2020
Linux - How to unlock and reset user’s account
Viewed 776 times since Fri, Jun 8, 2018
Linux Kernel /etc/sysctl.conf Security Hardening
Viewed 2527 times since Fri, Aug 3, 2018
RHEL: Manually encrypting a filesystem with LUKS
Viewed 1491 times since Sun, May 27, 2018
10 Linux nslookup Command Examples for DNS Lookup
Viewed 768 times since Sun, Sep 30, 2018
stunnel How To Set Up an SSL Tunnel Using Stunnel on Ubuntu
Viewed 158 times since Sun, Dec 6, 2020
zabbix linux How to solve apache error No space left on device: Cannot create SSLMutex
Viewed 213 times since Wed, Nov 11, 2020
RHEL: Force system to prompt for password in Single User mode
Viewed 2735 times since Sat, Jun 2, 2018
RHEL: udev rules basics
Viewed 1707 times since Sat, Jun 2, 2018