[lint-monster] LintMonster daily report — function-length backlog refreshed (670 findings)

[github-actions[bot]]

Daily lint scan summary

• make golint-custom is not clean
• Detected 670 largefunc findings total
• Breakdown: 287 in pkg/workflow, 383 in pkg/cli
• Root-cause grouping policy collapses all largefunc findings in pkg/workflow and pkg/cli into one shared topic: function-length refactoring

Group definitions and finding counts

1. function-length refactoring — 670 findings
   • Scope: all current largefunc diagnostics under pkg/workflow and pkg/cli
   • Representative hotspots:
     • pkg/workflow/awf_helpers.go — BuildAWFCommand (377 lines)
     • pkg/workflow/safe_outputs_config_extraction.go — extractSafeOutputsConfig (366 lines)
     • pkg/workflow/unified_prompt_step.go — generateUnifiedPromptCreationStep (259 lines)
     • pkg/cli/logs_download.go — downloadRunArtifacts (386 lines)
     • pkg/cli/mcp_tools_privileged.go — 6 findings in one file

Issues created or updated

• No issue was created or updated in this run.
• I identified existing authoritative/open trackers:
  • [lint-monster] Authoritative function-length refactoring tracker #49251 — authoritative function-length tracker
  • [lint-monster] function-length refactoring backlog snapshot (683 findings) #49700 — previous backlog snapshot
  • [lint-monster] Reduce custom lint function-length hotspots in pkg/workflow builders #49250 and [lint-monster] Reduce custom lint function-length hotspots in pkg/cli command flows #49252 — older slice trackers that now overlap with the shared-topic policy

Duplicate issues closed

• None

Why no tracker update occurred

The workflow currently lacks safe-output configuration that permits update_issue on a non-issue-triggered run. Attempting to refresh #49251 failed with:

update_issue requires an issue context ... use create_discussion or create_issue instead

Because of that limitation, this run could only publish this discussion report.

Agent assignments

• None

Groups skipped and why

• function-length refactoring execution work was not assigned because the required flow says to assign only when creating a new issue that needs execution work right now, and an authoritative open issue already exists ([lint-monster] Authoritative function-length refactoring tracker #49251).
• No additional groups were created because the current lint run contains only largefunc findings, which policy merges into one shared topic.

Fused remediation guidance for future slices

• Keep remediation scoped to the assigned lint group only.
• Prefer minimal, targeted helper extraction over broad rewrites.
• Preserve behavior, logging, output formatting, and generated YAML.
• Keep helpers file-local unless reuse is clearly warranted.
• Validate with make golint-custom before handoff.

Generated by 🧌 LintMonster · gpt54 · 22.6 AIC · ⌖ 4.8 AIC · ⊞ 5.4K · ◷

• expires on Aug 4, 2026, 7:48 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by LintMonster.

A newer discussion is available at Discussion #50165.