[daily-compiler-quality] Daily Compiler Code Quality Report - 2026-06-20 #40426
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-06-21T03:47:38.986Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🔍 Compiler Code Quality Analysis — 2026-06-20
Files Analyzed:⚠️ 2/3 files meet ≥75 threshold —
compiler_orchestrator_engine.go,compiler_safe_outputs_job.go,compiler_yaml.goStatus:
compiler_yaml.goremains belowExecutive Summary
All three files changed in commit
9ad5040. Changes are uniformly well-executed (magic-string → constants,map[string]bool→map[string]struct{}, clean feature additions). However, three large-function gaps flagged since 2026-06-14 remain unaddressed for the third consecutive cycle.Overall codebase (9 files): avg 78.4/100, 7/9 files meeting the quality threshold — stable vs last run.
Summary Table
compiler_orchestrator_engine.goapplyEngineImportDefaultsgrew to 82L with 4× repeated JSON-unmarshalcompiler_safe_outputs_job.gobuildSafeOutputsHandlerOutputsAndActionSteps221L (tracked 3+ cycles)compiler_yaml.gogeneratePrompt289L (tracked 3+ cycles); file growing to 1,089LAvg (today): 78/100 · Files meeting threshold: 2/3
📁 Detailed Scores
compiler_orchestrator_engine.go— 84/100Strengths:
MaxTurnCacheMissesaddition mirrors existing budget-limit pattern exactly ·enableFirewallByDefaultForPifollows copilot/Claude pattern · 100%%werror wrapping · test/source ratio improved to 1.52 (was 1.41)Issues:
applyEngineImportDefaultsgrew to 82L with 4×json.Unmarshal → parseMax* → assignblocks · comment density still low (~5.5%) · 6 barereturn nil, errwithout contextcompiler_safe_outputs_job.go— 78/100Strengths:
map[string]struct{}replacesmap[string]boolfor set deduplication (correct Go idiom) ·constants.TmpGhAwDirSlashreplaces 2 magic strings · removed unnecessarybuildExtractBaseBranchStep· 27% comment density · 1.58× test ratio · 100% error wrappingIssues:
buildSafeOutputsJobFromParts235L andbuildSafeOutputsHandlerOutputsAndActionSteps221L — both flagged every cycle since 2026-06-14 ·buildJobLevelSafeOutputEnvVars116L · file size 934Lcompiler_yaml.go— 73/100Strengths:
constants.GithubDirreplaces 2 magic".github/"strings ·CompilerVersionfallback is correct defensive code · newGH_AW_SAFE_OUTPUTS_URLSfollows surrounding env-var pattern · 1.45× test ratio · 100% error wrappingIssues:
generatePromptstill 289L (flagged 3+ cycles, no progress) · file grew to 1,089L (+6 this cycle, +9 over last 2 cycles) ·generateWorkflowHeader176L ·generateCreateAwInfo174L with engine-ID switch that should be amap[string]string📈 All-Files Historical Scorecard
Codebase avg: 78.4/100 · Meeting threshold: 7/9 (78%) — unchanged vs last run
Next rotation:
compiler.go,compiler_jobs.go,compiler_yaml_main_job.go(priority: last two at 79/67)Actionable Recommendations
High Priority
Extract JSON-unmarshal helper in
applyEngineImportDefaults(compiler_orchestrator_engine.go)json.Unmarshal → parse → assign if > 0blocks; aapplyMergedEngineIntLimithelper shrinks the function from 82L to ~40LSplit
generatePrompt(compiler_yaml.go)// Step 1a,// Step 1b,// Step 1.5,// Step 2commentsMedium Priority
buildSafeOutputsJobFromPartsinto phase-based helpers — phase comments already existgenerateCreateAwInfoswitch into amap[string]stringTop 3 Issues
generatePromptat 289L — chronic, 3+ cycles unaddressedbuildSafeOutputsHandlerOutputsAndActionStepsat 221L — chronic, 3+ cyclesapplyEngineImportDefaults— new this cycle, easy to fixRecommended Action
Extract the 4× JSON-unmarshal pattern in
applyEngineImportDefaultsinto a generic helper (30 min, highest ROI today; also prevents the pattern from being copied again on the next budget-limit addition).§27859033467 · Serena MCP + static analysis · Cache:
/tmp/gh-aw/cache-memory/compiler-quality/Beta Was this translation helpful? Give feedback.
All reactions