Add go fix check

[aleksandr4842]

📝 Description

Add check code by go fix

Fix code, and add this check to CI

🗣️ Type of Change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 📖 Documentation update
• ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

• 🤖 Fully AI-generated (100% AI, 0% Human)
• 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
• 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

📚 Technical Context (Skip for Docs)

• Reference URL:
• Reasoning:

🧪 Test Environment

• Hardware:
• OS:
• Model/Provider:
• Channels:

📸 Evidence (Optional)

Click to view Logs/Screenshots

☑️ Checklist

• My code/docs follow the style of this project.
• I have performed a self-review of my own changes.
• I have updated the documentation accordingly.

[xiaket]

Instead of bringing the changes, do you mind bringing the tooling into this repo so we are not tripped by this issue again?

Also please provide a description of this PR so we can better keep track of changes. Thank you!

Please address the concern above and re-request review.

[aleksandr4842]

@xiaket hello! Thank you for review. I added go fix check to CI

[xiaket]

LGTM, please wait for a second round of eyes from @imguoguo before getting this in.

[xiaket]

@aleksandr4842 do you mind taking a look at the failed build?

[aleksandr4842]

@xiaket fixed

[imguoguo]

Thanks for your contribution!

CI part LGTM, but this PR also touches other areas (including agent and provider), so it still needs review from the other two developers(@yinwm , @lxowalle).

(When merging with squash, please update the commit message header to follow this specification: https://www.conventionalcommits.org/en/v1.0.0/)

[lxowalle]

Hi @aleksandr4842, I'm not sure if go fix would change for i := 0; i < 5; i++ to for i := range 5 — my local tests show it doesn't. But this PR contains many similar changes. Can you confirm whether these changes were all made by go fix? Also, could we add go fix to the check command in the Makefile so developers can catch these issues earlier?

[aleksandr4842]

All changes in PR by go fix command

[imguoguo]

Hi @aleksandr4842, I'm not sure if go fix would change for i := 0; i < 5; i++ to for i := range 5 — my local tests show it doesn't. But this PR contains many similar changes. Can you confirm whether these changes were all made by go fix? Also, could we add go fix to the check command in the Makefile so developers can catch these issues earlier?

It does look odd indeed. I ran go fix ./... in the picoclaw directory on Fedora 43 with Go 1.25.7 at this commit(80c8b57), but it produced no changes. Is there something wrong with my operating method?

My version info is:

go version go1.25.7 X:nodwarf5 linux/amd64

[aleksandr4842]

I use go1.26. In this version go fix was changed...

[xiaket]

Thanks @aleksandr4842 ! In that case, we may want to close this PR and revisit at a later date, since the go version in go.mod is still on 1.25.7.