🔧 Integrate golangci-lint for Static Code Analysis

[Saurabh2402]

To improve code quality and maintain consistency across the project, I'd like to propose adding golangci-lint to our development workflow.

This tool helps catch common bugs, enforces style guidelines, and ensures adherence to Go best practices—all with minimal setup and configuration.

Why this matters:

• Identifies potential bugs early through static analysis
• Maintains consistent code style and formatting
• Reduces technical debt over time
• Speeds up code reviews with automated checks

Proposed steps:

• Add golangci-lint configuration file (.golangci.yml) to the root of the repository.
• Define rules and linters we want to enforce.
• Update documentation or contributing guide to include linting steps.
• Integrate it into the CI pipeline to auto-run checks on PRs.

Let me know your thoughts or if you'd like help setting up the initial config. 🚀

[github-actions]

This issue was automatically closed because it did not follow the issue template. We use the issue tracker exclusively for bug reports and feature additions that have been previously discussed. However, this issue appears to be a support request. Please use the discussion forums for support requests.

[jedisct1]

Just playing with AI tools?

[Saurabh2402]

Actually, no AI involved here, just thought linters could improve code quality and enforce best practices.
Well, even if AI suggested it, linters are a pretty solid win for any repo. Why not make clean code easier for everyone?

[Saurabh2402]

Check here few of the out of box suggestions to improve readbility:

[Saurabh2402]

@jedisct1 What do you say ?

[jedisct1]

Your message was AI generated by Claude :)

I generally prefer to run these scripts locally, so that it's easier to decide what's worth it and what would actually make maintenance more complicated.