Audit the current Go library across style, performance, readability, and usability, then apply small verified fixes that improve code health without changing public behavior unexpectedly.
- Phase 1: Plan and setup
- Phase 2: Repository review and quality gate baseline
- Phase 3: Record findings and prioritize fixes
- Phase 4: Implement focused fixes with tests
- Phase 5: Verify and deliver final report
- Which issues are correctness or usability risks versus optional style concerns?
- Which fixes can be made safely with small, reversible diffs?
- What tests or tooling prove behavior remains intact?
- Use
planning-with-filesas the requested plan-with-files workflow; keep this audit separate from the existingtask_plan.mdphase plan to avoid overwriting prior work. - Default to small, behavior-preserving fixes; avoid new dependencies.
- Standalone
staticcheckinstall viamisefailed because GitHub/Go module downloads timed out or were blocked by network/proxy connectivity; used existingmise-managedgolangci-lint, which includes staticcheck, and fixed all reported issues. golangci-lintinitially reported 19 issues; final run reports0 issues.
Complete - Audit, fixes, and verification finished.