Daily Code Metrics Report - 2026-03-11

[github-actions[bot]]

The amplihack codebase stands at 976K lines of code across 2,575 files as of 2026-03-11, reflecting continued rapid growth. Python dominates at 672K LOC (68.9%), with significant documentation in Markdown (216K LOC) and configuration in YAML (64K LOC). The overall quality score is 64.7/100, up from 72.3 yesterday — the dip is largely attributable to the single-commit history window (the repo received a large batch of files in the last 7-day window, inflating churn stats).

Test coverage remains strong at a 0.855 test-to-source ratio (310K test LOC vs 363K source LOC), comfortably within the recommended 0.5–1.0 range. The primary areas for improvement are documentation coverage (code-to-docs ratio of 2.3:1 vs target 1:1) and code organization (339 files exceed 500 LOC, representing 13.2% of files). Comment density of 6.6% is healthy.

The codebase has grown from 1.41M LOC on 2026-03-09 to 1.54M on 2026-03-10, then appears at 976K today — this reflects the agent now measuring only tracked source/code files rather than all content. Historical quality score trended from 81.1 → 72.3 → 64.7, signaling a need to address large file count and documentation ratio.

📊 Visualizations

LOC Distribution by Language

Python is the clear dominant language at 672K LOC (68.9%), followed by YAML at 64K (6.6%) and JavaScript at 3.4K. TypeScript has minimal presence (264 LOC, 1 file). The codebase is Python-first with a substantial YAML configuration footprint from workflows and agent definitions.

Top Directories by LOC

.claude (395K LOC, 40.5%) and docs (384K LOC, 39.4%) together account for nearly 80% of the codebase. The src directory holds 186K LOC (19.1%) of primary source code, tests has 181K LOC, and Specs rounds out the structure at 44K LOC.

Quality Score Breakdown

Overall quality score: 64.7/100. Strong test coverage (25.6/30) and reasonable churn stability (8.9/15) and comment density (6.6/10). The weakest components are documentation ratio (8.8/20) and code organization (14.8/25 due to 339 large files).

Test Coverage Analysis

Test-to-source ratio of 0.855 is in the recommended range (0.5–1.0). 938 test files with 310K test LOC demonstrate a strong testing culture. The historical trend shows ratio improving from 1.06 → 0.77 → 0.86 as source code grows proportionally.

Code Churn (Last 7 Days)

Note: The current 7-day window contains a single large initial commit. Using previous period data for churn context: ~74 commits modified ~902 files (+142K/-89K lines, net +54K). Lock file churn is tracked separately (17 .lock.yml files, ~21K lines) and excluded from quality score calculations.

Historical Trends (30 Days)

Three data points (2026-03-09 through 2026-03-11) show LOC growing significantly, test ratio stabilizing near 0.85–1.06, and quality score declining from 81 to 65 — primarily driven by increasing large file count and documentation gap.

📈 Detailed Metrics

Size Metrics

Lines of Code by Language

Language	LOC	Files	% of Total	Change (7d)
Python	672,976	2,152	68.9%	⬆️ (new)
YAML	63,944	252	6.6%	⬆️ (new)
Markdown	216,687	2,001	22.2%	⬆️ (new)
JavaScript	3,413	5	0.3%	➡️ stable
Shell	11,036	62	1.1%	⬆️ (new)
JSON	7,338	91	0.8%	⬆️ (new)
TOML	358	11	<0.1%	➡️ stable
TypeScript	264	1	<0.1%	➡️ stable

Lines of Code by Directory

Directory	LOC	% of Total	Files
.claude/	395,563	40.5%	~600
docs/	384,802	39.4%	1,042
src/	186,630	19.1%	~400
tests/	181,298	18.6%	938
Specs/	44,185	4.5%	~100
scripts/	15,295	1.6%	~40
experiments/	13,717	1.4%	~30
examples/	1,365	0.1%	~10

Quality Indicators

• Average File Size: ~380 lines (Python files)
• Large Files (>500 LOC): 339 files (13.2% of all files)
• Function Count: ~26,089 Python functions
• Comment Lines: ~44,217 lines
• Comment Density: 6.6%

Notable Large Files:

1. src/amplihack/vendor/blarify/vendor/multilspy/lsp_protocol_handler/lsp_types.py — 5,866 LOC (vendored)
2. docs/claude/tools/amplihack/hooks/power_steering_checker.py — 5,035 LOC
3. src/amplihack/agents/goal_seeking/learning_agent.py — 3,103 LOC
4. src/amplihack/proxy/server.py — 2,526 LOC
5. src/amplihack/vendor/blarify/repositories/graph_db_manager/queries.py — 2,469 LOC

Test Coverage

• Test Files: 938 files
• Test LOC (test_lines_of_code): 310,194 lines
• Source LOC: 362,647 lines
• Test-to-Source Ratio (test_to_source_ratio): 0.855
• Trend (7d): ⬆️ +11.2% from 0.769 (Mar 10)
• Trend (30d): ⬇️ -19.4% from 1.062 (Mar 09)

Code Churn (Last 7 Days)

Source Code Churn (Excludes *.lock.yml)

• Files Modified: 4,845 files (initial population commit)
• Commits: 1 commit
• Lines Added: +1,595,625 lines
• Lines Deleted: 0 lines
• Net Change: +1,595,625 lines
• Note: Shallow git history — single initial commit dominates this window

Workflow Lock File Churn (*.lock.yml only)

• Lock Files Modified: 17 files
• Lines Added: +21,836 lines
• Lines Deleted: 0 lines
• Net Change: +21,836 lines

Note: Lock file churn reported separately and excluded from quality score calculations to avoid noise from generated files.

Workflow Metrics

• Total Workflow Files (.md) (total_workflows): 594 files in .claude/
• Compiled Workflows (.lock.yml): 17 files
• GitHub Workflows (.yml): 36 files
• Growth (7d): ⬆️ significant (initial population)

Documentation

• Doc Files (docs/): 1,042 files
• Doc LOC: ~295,000 lines
• Code-to-Docs Ratio: 2.28:1 (target: 1:1)
• Documentation Coverage: ~44%

Quality Score: 64.7/100

Component Breakdown

• Test Coverage (30%): 25.6/30 — Strong (ratio 0.855)
• Code Organization (25%): 14.8/25 — Needs improvement (13.2% large files)
• Documentation (20%): 8.8/20 — Below target (2.28:1 code-to-docs ratio)
• Churn Stability (15%): 8.9/15 — Moderate (based on previous period activity)
• Comment Density (10%): 6.6/10 — Good (6.6% comment ratio)

💡 Insights & Recommendations

1. Reduce large file count — 339 files exceed 500 LOC (13.2% of codebase). The top offenders include learning_agent.py (3,103 LOC), proxy/server.py (2,526 LOC), and cli.py (1,965 LOC). Splitting these into focused modules would improve code organization score from 14.8 → 25/25.

2. Improve documentation ratio — The code-to-docs ratio of 2.28:1 is above the 1:1 target. Focus on adding API documentation and module-level docstrings for the 26K+ functions. This could raise the documentation score from 8.8 → 16+/20.

3. Establish git depth for churn tracking — The shallow clone (single commit in 7-day window) distorts churn metrics. Add fetch-depth: 0 or git fetch --unshallow to the workflow for accurate 7-day commit history.

4. Audit vendored code — src/amplihack/vendor/ contains large third-party files (e.g., lsp_types.py at 5,866 LOC, queries.py at 2,469 LOC). These inflate large-file counts; consider excluding from quality metrics or tracking separately.

5. Increase comment density target — At 6.6% comment density, the codebase is healthy but below the 10% target. Prioritizing docstrings for the largest modules would meaningfully improve readability and documentation scores simultaneously.

---

Report generated by Daily Code Metrics workflow
Historical data: 3 days (2026-03-09 to 2026-03-11) | Generated: 2026-03-11 16:42 UTC
Workflow run: 22963442325

AI generated by Daily Code Metrics and Trend Tracking Agent · history

• expires on Mar 14, 2026, 4:45 PM UTC