You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8 metrics tracked, 1 reporting gap flagged — codebase health is stable (Quality Score: 75.1/100, Good), but this report follows a 26-day gap since the last recorded run (2026-07-07 → 2026-08-02), so "7-day" deltas below actually span 26 days.
The repository grew to 2,068,245 LOC across 6,598 files (+11.7% since the last recorded snapshot). Test coverage remains very strong (test-to-source ratio 1.93, well above the 0.5–1.0 healthy range), documentation grew faster than code (+21.5% doc LOC), and churn stability is the weakest component of the quality score — 1,115 source files (~17% of the codebase) changed in the last 7 days, largely driven by a major docs rewrite (docs/src/content/docs/reference/frontmatter-full.md, net +9,273 lines).
📊 Visualizations
YAML (workflow lock files) and Go Tests are the two largest buckets, together ~53% of all LOC — expected for a workflow-compiler project with a heavy test suite.
pkg/ (39.5%) and .github/ (33.3%, mostly compiled workflow YAML) dominate; docs/ has grown to 6.2% of total LOC.
Test Coverage and Documentation are near-max; Churn Stability (6.6/15) and Code Organization (12.3/25) are the biggest opportunities.
Go test LOC (512K) is nearly 2x source LOC (265K) — comfortably above the recommended ceiling, suggesting a very thorough (if heavy) test suite.
The top churn file is a documentation rewrite, not source code; excluding it, churn is dominated by new integration tests and small refactors.
The visible jump between 07-07 and 08-02 reflects the 26-day reporting gap (annotated), not a single-day spike.
Investigate the reporting gap: no daily-code-metrics entries were recorded between 2026-07-07 and 2026-08-02 (26 days). Check whether this workflow was disabled, failing, or paused, since all "7-day" figures above actually cover that longer window.
Churn stability is the weakest component (6.6/15): ~17% of the codebase (1,115 files) changed in the last 7 days. Excluding the single large docs rewrite, source churn is still broad — consider batching related changes into fewer, larger PRs to reduce review overhead.
Code organization (12.3/25): 1,008 files exceed 500 LOC (15.3% of all files), concentrated in pkg/ (39.5% of total LOC). Consider splitting the largest files, especially any single files approaching 1,000+ LOC.
Comment density is low (6.4/10, 9.63% ratio): given the growing average Go file size (~224 LOC), more inline documentation would help future maintainers navigate pkg/.
Test-to-source ratio (1.93) is well above the 0.5–1.0 healthy range: this isn't necessarily bad, but periodically audit for redundant or overlapping test cases as the suite continues to outgrow source code 2:1.
💡 Next Actions
Confirm the daily-code-metrics workflow schedule/trigger is running as expected going forward (26-day gap detected).
Review the top churned source files for the current sprint's focus areas.
Consider a follow-up pass on large-file splitting in pkg/ to improve the Code Organization score.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Summary
8 metrics tracked, 1 reporting gap flagged — codebase health is stable (Quality Score: 75.1/100, Good), but this report follows a 26-day gap since the last recorded run (2026-07-07 → 2026-08-02), so "7-day" deltas below actually span 26 days.
The repository grew to 2,068,245 LOC across 6,598 files (+11.7% since the last recorded snapshot). Test coverage remains very strong (test-to-source ratio 1.93, well above the 0.5–1.0 healthy range), documentation grew faster than code (+21.5% doc LOC), and churn stability is the weakest component of the quality score — 1,115 source files (~17% of the codebase) changed in the last 7 days, largely driven by a major docs rewrite (
docs/src/content/docs/reference/frontmatter-full.md, net +9,273 lines).📊 Visualizations
YAML (workflow lock files) and Go Tests are the two largest buckets, together ~53% of all LOC — expected for a workflow-compiler project with a heavy test suite.
pkg/(39.5%) and.github/(33.3%, mostly compiled workflow YAML) dominate;docs/has grown to 6.2% of total LOC.Test Coverage and Documentation are near-max; Churn Stability (6.6/15) and Code Organization (12.3/25) are the biggest opportunities.
Go test LOC (512K) is nearly 2x source LOC (265K) — comfortably above the recommended ceiling, suggesting a very thorough (if heavy) test suite.
The top churn file is a documentation rewrite, not source code; excluding it, churn is dominated by new integration tests and small refactors.
The visible jump between 07-07 and 08-02 reflects the 26-day reporting gap (annotated), not a single-day spike.
View Full Details
Size
*_test.go)pkg/— 816,647 LOC (39.5%)Quality
.go).go)Tests
Churn — Source (7d, excl.
*.lock.yml/actions-lock.json)Churn — Generated files (7d,
*.lock.yml/actions-lock.jsononly)Workflows / Docs
.md).lock.ymlfilesdocs/**/*.md)Trend deltas (⚠️ comparison base is 26 days old for "7d", 30 days old for "30d" due to the reporting gap)
Quality Score breakdown (weighted average, 100 pts total)
Recommendations
pkg/(39.5% of total LOC). Consider splitting the largest files, especially any single files approaching 1,000+ LOC.pkg/.💡 Next Actions
daily-code-metricsworkflow schedule/trigger is running as expected going forward (26-day gap detected).pkg/to improve the Code Organization score.All reactions