lint-check

To run pre-commit hooks and golangci-lint on modified Go files before finishing work, use this Skill to execute checks on changed files, enforce formatting and lint rules, and re-run checks after applying fixes.

The best way to verify Go code quality before opening a pull request is to run pre-commit hooks and golangci-lint on modified files, ensuring all formatting and lint checks pass according to your project's configuration.

Yes, this lint check process works with existing Go modules and project configurations by running golangci-lint and pre-commit hooks that report results based on the rules already defined in your repository.

You need to run golangci-lint and pre-commit checks during your workflow when preparing commits, pull requests, or releases after code changes, ensuring formatting and safety issues are caught before completion.

Yes, you can fix code quality issues automatically because the Skill identifies issues, allows you to apply fixes, and then re-runs the pre-commit and golangci-lint checks to verify that the modified files now pass.

Your golangci-lint check fails on modified files before a commit because the code contains formatting, style, or safety issues that violate the project's lint configuration, requiring fixes before the checks can pass.