You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
make golint-custom reports 32 custom-linter findings in pkg/linters, separate from the shared pkg/workflow + pkg/cli function-length backlog.
Representative diagnostics
pkg/linters/mapclearloop/mapclearloop.go: run is 125 lines
pkg/linters/errorfwrapv/errorfwrapv.go: run is 117 lines
pkg/linters/seenmapbool/seenmapbool.go: inspectBody is 116 lines
pkg/linters/mapdeletecheck/mapdeletecheck.go: run is 109 lines
pkg/linters/writebytestring/writebytestring.go: run is 92 lines
Root cause
Several analyzer run functions and related literals/helpers have accumulated traversal, reporting, and fix-generation logic in a single block.
Expected outcome
Reduce the pkg/linters long-function count by extracting narrowly-scoped helpers in the worst analyzer hotspots while preserving diagnostics and suggested-fix behavior.
Remediation checklist
Keep remediation scoped to pkg/linters findings in this group
Prioritize the highest-length analyzer files first
Prefer minimal helper extraction and shared utility shaping over behavior changes
Preserve analyzer messages, positions, and fixes
Validate with make golint-custom
Fused skill guidance
Validate fixes by running make golint-custom
Keep remediation scoped to findings in the assigned lint group
Prefer minimal, targeted code edits
Copilot execution brief
Work only on the pkg/linters long-function findings from this lint run. Start with the highest-length analyzer hotspots (mapclearloop, errorfwrapv, seenmapbool, mapdeletecheck, writebytestring) and reduce the custom-linter count through small helper extraction and localized restructuring. Preserve analyzer semantics and suggested fixes. Run make golint-custom before finishing.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
pi.dev
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Lint group summary
make golint-customreports 32 custom-linter findings inpkg/linters, separate from the sharedpkg/workflow+pkg/clifunction-length backlog.Representative diagnostics
pkg/linters/mapclearloop/mapclearloop.go:runis 125 linespkg/linters/errorfwrapv/errorfwrapv.go:runis 117 linespkg/linters/seenmapbool/seenmapbool.go:inspectBodyis 116 linespkg/linters/mapdeletecheck/mapdeletecheck.go:runis 109 linespkg/linters/writebytestring/writebytestring.go:runis 92 linesRoot cause
Several analyzer
runfunctions and related literals/helpers have accumulated traversal, reporting, and fix-generation logic in a single block.Expected outcome
Reduce the
pkg/linterslong-function count by extracting narrowly-scoped helpers in the worst analyzer hotspots while preserving diagnostics and suggested-fix behavior.Remediation checklist
pkg/lintersfindings in this groupmake golint-customFused skill guidance
make golint-customCopilot execution brief
Work only on the
pkg/linterslong-function findings from this lint run. Start with the highest-length analyzer hotspots (mapclearloop,errorfwrapv,seenmapbool,mapdeletecheck,writebytestring) and reduce the custom-linter count through small helper extraction and localized restructuring. Preserve analyzer semantics and suggested fixes. Runmake golint-custombefore finishing.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
pi.devSee Network Configuration for more information.