# Shell scripts

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/go/2026.3/llms.txt).

GoLand provides coding assistance for shell script files: [completion](auto-completing-code.html) (including local paths), highlighting,   textual rename refactoring, and more.

[Video](https://resources.jetbrains.com/help/img/idea/2026.3/shellscript_assistance.mp4)

It also includes a special type of  [run/debug configurations](run-debug-configuration-shell-script.html)  for shell scripts.

GoLand integrates with several external tools to enhance shell script support:

* [ShellCheck](https://github.com/koalaman/shellcheck) is a shell script static analysis tool that can detect syntax errors, semantic problems, corner cases, and typical pitfalls. GoLand will prompt you to install it if it is not available. You can configure ShellCheck inspections in `Settings | Editor | Inspections | Shell Script`.

* [Shfmt](https://github.com/mvdan/sh) is an external formatter engine for shell scripts. GoLand will suggest installing it when you [reformat code](reformat-and-rearrange-code.html) `Ctrl+Alt+L` (Windows), `⌘ ⌥ L` (macOS), `⌘ ⌥ L` (IntelliJ IDEA Classic (macOS)), `⌘ ⌥ L` (macOS System Shortcuts), `Ctrl+Alt+L` (XWin), `Ctrl+Alt+L` (GNOME), `Alt+Shift+L` (KDE), `Ctrl+Alt+L` (Emacs), `Ctrl+Alt+L` (Sublime Text), `⌘ ⌥ L` (Sublime Text (macOS)), `Alt+Shift+F` (VSCode), `⌥ ⇧ F` (VSCode (macOS)) of the shell script for the first time. You can add the formatter manually in `Settings | Editor | Code Style | Shell Script`.

* [Explainshell](https://explainshell.com/) is a website that can parse any shell command and provide help text for each argument. Access to it is available via an [intention action](intention-actions.html): press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `Ctrl+.` (VSCode), `⌘ .` (VSCode (macOS)) and select Explain shell. The [Explainshell](https://explainshell.com/) website then opens with the description of the selected command.

Procedure: Enable the Shell Script plugin

This functionality relies on the [Shell Script](https://plugins.jetbrains.com/plugin/13122-shell-script)  plugin, which  is bundled and enabled in GoLand   by default. If the relevant features are not available, make sure that you did not disable the plugin.

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS)) to open settings and then select `Plugins`.

2. Find the Shell Script plugin and click Enable.

Procedure: Configure file types to be recognized as shell scripts

By default, GoLand recognizes files with the following extensions as shell scripts: `.sh`, `.bash`, `.zsh`. However, you can configure GoLand to recognize any file types as shell script files (for example, if you want to edit `.csh` files).

1. In the Settings dialog (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS))), select Editor | File Types.

2. In the Recognized File Types list, select Shell Script and add the necessary patterns in the File Name Patterns list below.

3. Click OK to apply changes.

Procedure: Run shell script files

* When working on a shell script file, click ![The Run icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.run.run.svg) in the gutter. This will run your script in the built-in [Terminal](terminal-emulator.html).

If you want to customize the startup of your script (for example, specify the script and interpreter options), you can also create a Shell Script [run/debug configuration](#shell-scripts-configurations).

> **Note:**
> If you run a script from the gutter icon and do not specify the shebang in your script, GoLand will use your default system interpreter defined by the `SHELL` environment variable. If you create a Shell Script run/debug configuration for a script file, GoLand will use the interpreter specified in the Interpreter path field of that configuration.

Procedure: Create configurations for script files

1. In the main menu, go to `Run | Edit Configurations`.

2. Click ![The Add button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg) and select Shell Script.

3. Under Execute, select the Script file option.

4. Specify the path to the script file and options that you want to pass to the script when it is launched. You can also change the interpreter for running the script and additional options for the interpreter.

5. Click OK to save the run/debug configuration.

Procedure: Create configurations for Shell commands

You can create a Shell Script run/debug configuration for simple arbitrary commands without creating a script file. This can be useful, for example, if you want to automatically run this command before another configuration is launched and do not want to create a separate file for it.

1. In the main menu, go to `Run | Edit Configurations`.

2. Click ![The Add button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.general.add.svg) and select Shell Script.

3. Under Execute, select the Script text option.

4. Enter the command text and, optionally, change the command working directory.

5. Click OK to save the run/debug configuration.

![Shell Script run/debug configuration](https://resources.jetbrains.com/help/img/idea/2026.3/shell_script_configuration_for_command.png)

If you want to run this command before another configuration (for example, another script) is launched, you can select the created configuration in the [Before launch](null) area of another configuration.

