🔧 Integrate golangci-lint for Static Code Analysis

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. 🚀