Point this at your Go project and it runs staticcheck across the whole thing.
It finds the issues, fixes them, then runs staticcheck again to make sure nothing’s left.
Staticcheck goes further than go vet.
It’ll catch deprecated API usage, pointless type conversions, slow string operations, and those bugs that compile just fine but break at runtime.
The kind of stuff that slips through code review.
Good for CI, pre-commit hooks, or just a periodic cleanup when your codebase has been accumulating lint.
Prompt
Analyze the Go codebase using `staticcheck` to find potential issues.
## Instructions:
1. Run `staticcheck ./...` to check the entire codebase
2. Analyze any reported issues
3. Fix all identified problems
4. If fixes were made, run `staticcheck ./...` again to verify they were resolved
5. If no issues were found initially or all issues were fixed, confirm that the code passes all checks
## Expected output:
- List of identified issues (if any)
- Description of fixes implemented
- Confirmation that all issues are resolved