[daily-code-metrics] Daily Code Metrics Report - 2026-07-09

[github-actions[bot]]

The gh-aw codebase stands at 1,861,736 total LOC across 5,815 tracked files, with a computed quality score of 72.0 / 100 — essentially flat versus the 07-07 baseline (72.3, −0.3) and down ~4% from a week ago (75.2 on 07-02). Growth remains steady and healthy: LOC is up +2.0% (7d) and +11.0% (30d), driven mostly by generated YAML/lock artifacts and continued Go test expansion. The test-to-source ratio of 1.96 is excellent (test coverage component maxed at 30/30), reflecting a strongly test-first codebase.

The score's soft spots are code organization (11.6/25) and churn stability (7.6/15). Large files (>500 LOC) sit at 936 — 16.1% of all tracked files — and 7-day source churn touched 1,161 files with a net +35,799 lines. The heaviest single-file movement came from action_pins.json data regenerations (±1,600 lines each) and a large refactor of pkg/parser/remote_fetch.go (−1,608). Documentation improved slightly: the code-to-docs ratio tightened to 2.76 (from 2.83), lifting the documentation component to 16.2/20.

No metric crossed a concerning threshold today. The main watch items are the persistently high large-file count and the volume of source churn — both actionable through targeted refactoring rather than urgent fixes. Note that historical large_files and doc_files counts show run-to-run methodology variance in the stored series, so the most reliable comparison is against the 07-07 entry (same methodology).

📊 Visualizations

YAML (496K) and Go Tests (473K) dominate; generated CJS JavaScript (282K) is the third-largest slice.

pkg/ (755K) and .github/ (607K) hold the bulk of the codebase; core dirs highlighted in green.

Test coverage is maxed (30/30); code organization and churn stability are the largest gaps to target.

473K test LOC against 241K source LOC — a 1.96 ratio, well above the recommended 0.5–1.0 band.

7-day source churn (lock files excluded) is concentrated in action_pins.json regenerations and parser refactors.

30-day view: LOC climbing steadily while test coverage % and quality score hold roughly flat.

📈 Detailed Metrics

Size (7d / 30d change)

Metric	Value	7d	30d
Total LOC	1,861,736	+2.0% ⬆️	+11.0% ⬆️
Total files	5,815	+1.0% ➡️	+15.1% ⬆️
Go files	2,456	—	—
Test files	1,407	+1.9% ⬆️	+10.5% ⬆️
Top languages	YAML 496K · Go Tests 473K · JS-CJS 282K · Markdown 272K · Go Source 241K
Top directories	pkg 755K · .github 607K · actions 305K · docs 109K

Quality

Metric	Value	7d	30d
Large files (>500 LOC)	936	+1.6% ⬆️	+161% ⬆️*
Avg Go source file size	229.6 LOC	—	—
Function count (Go)	15,831	—	—
Comment lines	70,267	—	—
Comment ratio	9.85%	+0.2% ➡️	−1.3% ⬇️

Tests

Metric	Value	7d	30d
Test files	1,407	+1.9% ⬆️	+10.5% ⬆️
Test LOC	472,725	—	—
Source LOC	240,857	—	—
Test:source ratio	1.963	−0.1% ➡️	−2.4% ⬇️

Churn — source (7d, lock files excluded)

Metric	Value
Files modified	1,161
Commits	339
Lines added / deleted	+53,456 / −17,657
Net change	+35,799

Churn — generated / lock files (7d)

Metric	Value
Files modified	261
Lines added / deleted	+56,282 / −55,545
Net change	+737

Workflows & Docs

Metric	Value	7d	30d
Agentic workflows (.md)	356	+0.3% ➡️	+4.4% ⬆️
Compiled lock files (.lock.yml)	256	−0.8% ➡️	—
Avg workflow size (.md)	233.8 LOC	—	—
Doc files (.md/.mdx)	565	−10.3% ⬇️*	+47% ⬆️*
Doc LOC	87,230	—	—
Code-to-docs ratio	2.76	improved from 2.83

_{*Large-file and doc-file counts show methodology variance across the historical series; compare against the 07-07 entry for a like-for-like read.}

Quality Score Breakdown — 72.0 / 100

Component	Weight	Score	Notes
Test coverage	30	30.0	ratio 1.96 ≥ target 1.0 (maxed)
Code organization	25	11.6	16.1% of files exceed 500 LOC
Documentation	20	16.2	code:docs 2.76, close to ideal ≤2.24
Churn stability	15	7.6	1,161 source files touched in 7d
Comment density	10	6.6	9.85% comment ratio (target 15%)

💡 Recommendations

1. Attack the large-file backlog. 936 files exceed 500 LOC (16.1% of the tree). Prioritize the largest Go source files in pkg/ for extraction/decomposition — this is the single biggest lever on the code-organization component (11.6/25).
2. Stabilize action_pins.json regeneration. The two action_pins.json copies dominate source churn (±1,600 lines each per run). Consider deduplicating to a single source of truth or excluding regenerated data blobs from source-churn accounting.
3. Lift comment density. At 9.85% (target 15%), exported Go APIs and complex functions would benefit from doc comments — a low-risk gain of up to ~3.4 points on the score.
4. Keep documentation momentum. The code-to-docs ratio improved to 2.76; pushing toward ≤2.24 would max the documentation component (20/20).
5. Monitor churn volatility. Net +35,799 source lines in 7 days is high; ensure large refactors (e.g. remote_fetch.go) land behind tests to protect the strong 1.96 test ratio.

References: §29042654541

Generated by 📊 Daily Code Metrics and Trend Tracking Agent · 236.8 AIC · ⌖ 39.1 AIC · ⊞ 8.3K · ◷

• expires on Jul 12, 2026, 11:17 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Daily Code Metrics and Trend Tracking Agent.

A newer discussion is available at Discussion #44817.