Highly extensible Go source code linter providing checks currently missing from other linters.
There is never too much static code analysis. Try it out.
#opinionatedchecks with very strict and specific requirements
gocritic doc <checkname>gives a checker description
The latest documentation is available at go-critic.github.io.
For most users, using
go-critic under golangci-lint is enough.
go-critic binaries can be found at releases page.
Instructions below show how to build
go-critic from sources.
GO111MODULE=on go get -v -u github.com/go-critic/go-critic/cmd/gocritic
If the command above does not work, you can try cloning this repository
GOPATH and run
gocritic executable is under your
Usage of gocritic:
gocritic [sub-command] [sub-command args...]
gocritic without arguments to get help output.
Supported sub-commands: check - run linter over specified targets $ gocritic check -help $ gocritic check -v -enable='paramTypeCombine,unslice' strings bytes $ gocritic check -v -enable='#diagnostic' -disable='#experimental,#opinionated' ./... version - print linter version $ gocritic version doc - get installed checkers documentation $ gocritic doc -help $ gocritic doc $ gocritic doc checkerName
check sub-command examples:
# Runs all stable checkers on `fmt` package: gocritic check fmt # Run all stable checkers on `pkg1` and `pkg2` gocritic check pkg1 pkg2 # Run all stable checkers on `fmt` package and configure rangeExprCopy checker gocritic check [email protected] 128 fmt # Runs specified checkers on `fmt` package: gocritic check -enable elseif,paramName fmt # Run all stable checkers on current dir and all its children recursively: gocritic check ./... # Like above, but without `appendAssign` check: gocritic check -disable=appendAssign ./... # Run all stable checkers on `foo.go` file: gocritic check foo.go # Run stable diagnostics over `strings` package: gocritic check -enable='#diagnostic' -disable='#experimental' strings # Run all stable and non-opinionated checks: gocritic check -enableAll -disable='#experimental,#opinionated' ./src/...
To get a list of available checker parameters, run
gocritic doc <checkerName>.
In place of a single name, tag can be used. Tag is a named checkers group.
#diagnostic- kind of checks that detect various errors in code
#style- kind of checks that find style issues in code
#performance- kind of checks that detect potential performance issues in code
#experimental- check is under testing and development. Disabled by default
#opinionated- check can be unwanted for some people. Disabled by default
This project aims to be contribution-friendly.
We're using an optimistic merging strategy most of the time. In short, this means that if your contribution has some flaws, we can still merge it and then fix them by ourselves. Experimental and work-in-progress checkers are isolated, so nothing bad will happen.
Code style is the same as in Go project, see CodeReviewComments.
See CONTRIBUTING.md for more details. It also describes how to develop a new checker for the linter.