Split oversized test files that violate the repo's own file-size convention
Description: The developer-code-organization skill mandates files of 100–500 lines (800+ only for "core infrastructure"), yet 30 test files exceed 1,500 lines and 17 exceed 2,000 lines. Per today's Repository Quality Report (discussion #53697): pkg/workflow/compiler_jobs_test.go (4,511 lines / 84 test funcs), compiler_safe_outputs_config_test.go (3,836 lines / 48 funcs), threat_detection_test.go (3,420 lines / 61 funcs), copilot_engine_test.go (3,311 lines / 57 funcs), and maintenance_workflow_test.go (3,076 lines / 31 funcs) all group tests by broad subsystem rather than narrower feature boundaries. The repo has a documented precedent for this exact kind of split (frontmatter.go → 5 focused files, cited in the skill itself).
Expected Impact: Splitting the largest 1-2 files by functional area (job type, safe-output kind, threat category) reduces merge-conflict risk on high-traffic test files, speeds up editor/LSP responsiveness, and makes it easier for humans and Copilot agents to locate the right test. Start with compiler_jobs_test.go, the single largest offender at 5.6× the 800-line ceiling.
Suggested Agent: New Agent (or general refactoring agent) modeled on the frontmatter.go split precedent
Estimated Effort: Medium (1-4 hours) per file
Data Source: DeepReport analysis, 2026-08-18 18:23Z cycle, discussion #53697.
Generated by 🔬 Deep Report · agent · 155.1 AIC · ⌖ 9.71 AIC · ⊞ 11.9K · ◷
Split oversized test files that violate the repo's own file-size convention
Description: The
developer-code-organizationskill mandates files of 100–500 lines (800+ only for "core infrastructure"), yet 30 test files exceed 1,500 lines and 17 exceed 2,000 lines. Per today's Repository Quality Report (discussion #53697):pkg/workflow/compiler_jobs_test.go(4,511 lines / 84 test funcs),compiler_safe_outputs_config_test.go(3,836 lines / 48 funcs),threat_detection_test.go(3,420 lines / 61 funcs),copilot_engine_test.go(3,311 lines / 57 funcs), andmaintenance_workflow_test.go(3,076 lines / 31 funcs) all group tests by broad subsystem rather than narrower feature boundaries. The repo has a documented precedent for this exact kind of split (frontmatter.go→ 5 focused files, cited in the skill itself).Expected Impact: Splitting the largest 1-2 files by functional area (job type, safe-output kind, threat category) reduces merge-conflict risk on high-traffic test files, speeds up editor/LSP responsiveness, and makes it easier for humans and Copilot agents to locate the right test. Start with
compiler_jobs_test.go, the single largest offender at 5.6× the 800-line ceiling.Suggested Agent: New Agent (or general refactoring agent) modeled on the frontmatter.go split precedent
Estimated Effort: Medium (1-4 hours) per file
Data Source: DeepReport analysis, 2026-08-18 18:23Z cycle, discussion #53697.