[daily-compiler-quality] Daily Compiler Code Quality Report - 2026-05-31

[github-actions[bot]]

🔍 Compiler Code Quality Analysis Report

Analysis Date: 2026-05-31 · Files Analyzed: compiler.go, compiler_jobs.go, compiler_yaml.go
Overall Status: ⚠️ One file below quality threshold — downward trend warrants attention

---

Executive Summary

Today's rotation analyzed three core compiler files via Serena Go LSP. The codebase shows a downward trend on commit 3628a8ea: compiler.go dropped 9 pts (85→76), compiler_yaml.go continued its 3-run decline (76→69→67), and only compiler_jobs.go recovered slightly (+1 to 77).

compiler_yaml.go (67/100) is now below the 75-pt threshold, driven by very long functions (up to 248 lines) and minimal error wrapping (5 fmt.Errorf calls for 1,023 lines). compiler.go has zero fmt.Errorf calls. compiler_jobs.go (31 wraps) is the model to emulate.

---

Summary Table

File	Score	Rating	Largest Function	Top Issue
compiler.go	76/100	✅ Good	CompileWorkflowData ~157 lines	0 fmt.Errorf calls
compiler_jobs.go	77/100	✅ Good	buildCustomJobs ~353 lines	1,028-line file
compiler_yaml.go	67/100	⚠️ Acceptable	generatePrompt ~248 lines	3rd consecutive decline

Avg: 73/100 · Meeting threshold (≥75): 2/3

---

📁 Detailed Score Breakdowns

compiler.go — 76/100

Dimension	Score	Max
Structure	20	25
Readability	14	20
Error Handling	12	20
Testing	18	20
Patterns	12	15

Strengths: Well-documented exports, 33% comment density, 2.03× test ratio (1,095 lines)
Issues: 0 fmt.Errorf calls — bare errors propagated; CompileWorkflowData 157 lines

compiler_jobs.go — 77/100

Dimension	Score	Max
Structure	15	25
Readability	13	20
Error Handling	18	20
Testing	19	20
Patterns	12	15

Strengths: 31 fmt.Errorf + 22 if err guards; 3.6× test ratio (3,700 lines); 23 symbols well-named
Issues: buildCustomJobs is 353 lines (lines 514–867); file at 1,028 lines

compiler_yaml.go — 67/100

Dimension	Score	Max
Structure	13	25
Readability	12	20
Error Handling	13	20
Testing	17	20
Patterns	12	15

Strengths: 24% comment density; 1.4× test ratio (1,440 lines)
Issues: generatePrompt 248 lines, generateWorkflowHeader 175 lines, generateCreateAwInfo 164 lines; only 5 fmt.Errorf calls

---

📈 Historical Trends

File	May-26/27	May-28	May-29	May-31	Trend
compiler.go	83	—	85	76	⬇️ -9
compiler_jobs.go	82	76	—	77	↔️ +1
compiler_yaml.go	76	69	—	67	⬇️ -2
compiler_yaml_main_job.go	—	75	—	—	—
compiler_safe_outputs.go	—	—	94	—	—
compiler_safe_outputs_job.go	—	—	76	—	—
compiler_orchestrator.go	98	—	—	—	—

Date	Avg Score	Files Below Threshold
2026-05-26	83	0
2026-05-28	73	0
2026-05-29	85	0
2026-05-31	73	1

---

Actionable Recommendations

1. Add fmt.Errorf wrapping in compiler.go (30–45 min) — zero wraps; would push score from 76 to ~82
2. Split generatePrompt in compiler_yaml.go (2–3 hrs) — extract engine-specific helpers ≤50 lines each
3. Split buildCustomJobs in compiler_jobs.go (3–4 hrs) — extract step/env/dependency logic
4. Increase error surface in compiler_yaml.go (1–2 hrs) — add validation returns to YAML builders

---

Top 3 Issues

1. compiler_yaml.go function sizes — generatePrompt 248 lines (3rd consecutive decline)
2. Zero fmt.Errorf wrapping in compiler.go
3. buildCustomJobs at 353 lines in compiler_jobs.go

Recommended Action

Priority: Add fmt.Errorf wrapping to compiler.go — highest ROI, ~30 min, pushes score from 76→82.

---

💾 Cache & Next Schedule

Commit analyzed: 3628a8ea (all files changed vs previous e1e656bd)
Total runs: 5 · Files analyzed today: 3

Next rotation: compiler_safe_outputs_job.go (76, May-29) · compiler_yaml_main_job.go (75, May-28) · compiler_safe_outputs.go (94, May-29)

---

Daily Compiler Quality Check · Serena MCP Server (Go LSP) · §26702302236

Generated by 📊 Daily Compiler Quality Check · sonnet46 3.9M · ◷

• expires on Jun 1, 2026, 3:46 AM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-06-01T03:46:33.193Z.

Closed by Workflow