clean

You can check shell script quality by running static analysis with shellcheck and formatting with shfmt across your codebase. This process identifies potential bugs, syntax errors, and ensures consistent 4-space indentation for improved readability.

The best way to lint shell scripts before a commit is to run automated static analysis using shellcheck. This catches potential bugs and syntax errors early, ensuring a clean codebase and preventing formatting issues from reaching your repository.

Yes, you need both shellcheck and shfmt installed for full functionality. Shellcheck handles static analysis to find bugs, while shfmt automatically formats your shell scripts according to a consistent style with 4-space indentation.

Yes, you can use shfmt to automatically format shell scripts and fix styling errors. It enforces consistent code formatting with 4-space indentation, addressing stylistic issues and improving readability across your project.

Shellcheck reports syntax errors because it performs static analysis to identify potential bugs and stylistic issues in shell scripts. Running this check helps address code quality problems and prevents errors before committing new scripts.

You need to run shell script quality checks before committing new scripts or making significant changes. This pre-commit quality gate uses shellcheck and shfmt to automatically catch and fix linting and formatting errors.