shellcheck

FIRST-HAND READS

What people reported, in their own words. Every line links to where it was said.

• “shellcheck is a huge help in the middle sized shell script space and will regularly shout at me about missing all the random gotchas like not quoting file paths”

  POSITIVE · ease of use · Hacker News · 2026-06-28

• “I prefer to have no shellcheck errors/warnings by default so when they do appear it's very obvious”

  POSITIVE · features · Hacker News · 2026-03-29

• “Shellcheck was a big game changer at least in terms of learning some of the nuance from a "best practice" standpoint.”

  POSITIVE · features · Hacker News · 2026-02-27

• “all scripts have to pass ShellCheck to "build". They can't be deployed or committed with obvious parse errors or ambiguities around quoting or typos in variable names.”

  POSITIVE · reliability · Hacker News · 2026-01-28

• “they're linted by ShellCheck, thanks to some experimental changes I made to Devenv's scripts module”

  POSITIVE · ease of use · Hacker News · 2025-12-15

• “I have had a problem with shellcheck that for some reason eats up all my ram when I open I believe .zshrc and trust me, it's not invisible. The system crawls to a halt.”

  NEGATIVE · performance · Hacker News · 2025-10-21

• “Shellcheck has been a huge game changer for me. The lack of a linter is the main reason I don't consider switching to zsh anymore. When I first found shellcheck, I'd sit on the train every morning and fix all the stupid little bugs in all our shell code. I learned a TON about shell scripting, because the shellcheck wiki is amazing.”

  POSITIVE · features · Hacker News · 2025-08-11

• “I rather dislike shellcheck because it combines genuine smells with opinions, such as insisting on $(...) instead of `...`”

  NEGATIVE · features · Hacker News · 2025-07-26

• “passes `shellcheck ./script.sh` (or, any other static analysis) first. I don't like fixing other people's bugs in their installation scripts.”

  POSITIVE · features · Hacker News · 2025-07-24

• “shellcheck tells me to write `"$@"` and `"${@:$#}"` so quotes are indeed needed”

  POSITIVE · features · Hacker News · 2025-07-13

• “I already use ShellCheck, by the way. It's a must, and it helps a lot when reviewing LLM output.”

  POSITIVE · features · Hacker News · 2025-07-05

• “run it through `shellcheck`, and ask for my explicit OK before executing”

  POSITIVE · features · Hacker News · 2025-06-28

• “Making a lot of noise about use of (the shellcheck author's) non-preferred syntax, which works perfectly fine in a given context, is a design flaw that renders shellcheck useless to me.”

  NEGATIVE · features · Hacker News · 2025-03-05

• “I learned more Bash and Python from running Shellcheck and Ruff respectively”

  POSITIVE · ease of use · Hacker News · 2024-12-24

• “Using ShellCheck as a linter can catch a lot of the common footguns”

  POSITIVE · features · Hacker News · 2024-12-07

• “it means that I don't trigger any ShellCheck warnings for them and it's easier to just type the extra characters than thinking about whether or not they'll actually make any difference”

  POSITIVE · ease of use · Hacker News · 2024-09-15

• “My experience with shellcheck is that it mostly finds false positives that waste my time.”

  NEGATIVE · performance · Hacker News · 2024-09-14

• “long scripts benefit far more from using ShellCheck as you're more likely to make mistakes and are less likely to spot them”

  POSITIVE · features · Hacker News · 2024-09-14

• “I'd much rather use vim and shellcheck, and have all of Unix at my command”

  POSITIVE · Hacker News · 2024-07-27