Description
The Repository Quality Improvement Report (2026-08-24) flagged pkg/workflow/safe_outputs_handler_registry.go as the single largest source file in the repo at 1,091 lines (verified via wc -l) — a single map literal (handlerRegistry) holding 49 inline closures, one per safe-output handler key (create_issue, add_comment, create_pull_request, etc.). This directly fights the repo's own developer-code-organization convention (100–500 lines/file, one file per functionality), which this same package already follows elsewhere (create_issue.go at 160 lines is cited as the exemplar).
Split the registry by handler category into multiple smaller files (e.g. one file per logical grouping of related safe-output handlers), leaving safe_outputs_handler_registry.go as a thin file that just assembles the map from the per-file builder functions. This is a pure code-organization move — no behavior change, since each closure is self-contained.
Expected Impact
Improves reviewability and reduces merge-conflict surface in a file the report notes was "touched today" (i.e. still actively changing, so the decomposition debt is accumulating rather than sitting in stable legacy code).
Suggested Agent
New Agent / general coding agent — mechanical extraction, verify via existing safe-output handler tests after the split.
Estimated Effort
Medium (1-4 hours).
Data Source
DeepReport Intelligence Briefing analysis, 2026-08-24 cycle, mining Repository Quality Improvement Report #55409. File size and line count independently reverified via wc -l before filing.
Generated by 🔬 Deep Report · claude · agent · 267.3 AIC · ⌖ 9.56 AIC · ⊞ 12.4K · ◷
Description
The Repository Quality Improvement Report (2026-08-24) flagged
pkg/workflow/safe_outputs_handler_registry.goas the single largest source file in the repo at 1,091 lines (verified viawc -l) — a single map literal (handlerRegistry) holding 49 inline closures, one per safe-output handler key (create_issue,add_comment,create_pull_request, etc.). This directly fights the repo's owndeveloper-code-organizationconvention (100–500 lines/file, one file per functionality), which this same package already follows elsewhere (create_issue.goat 160 lines is cited as the exemplar).Split the registry by handler category into multiple smaller files (e.g. one file per logical grouping of related safe-output handlers), leaving
safe_outputs_handler_registry.goas a thin file that just assembles the map from the per-file builder functions. This is a pure code-organization move — no behavior change, since each closure is self-contained.Expected Impact
Improves reviewability and reduces merge-conflict surface in a file the report notes was "touched today" (i.e. still actively changing, so the decomposition debt is accumulating rather than sitting in stable legacy code).
Suggested Agent
New Agent / general coding agent — mechanical extraction, verify via existing safe-output handler tests after the split.
Estimated Effort
Medium (1-4 hours).
Data Source
DeepReport Intelligence Briefing analysis, 2026-08-24 cycle, mining Repository Quality Improvement Report #55409. File size and line count independently reverified via
wc -lbefore filing.