Daily Code Metrics Report - 2026-03-04 #175
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-07T19:55:05.111Z.
|
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.
-
The tt2 repository sits at 145,649 total lines of code across 278 files as of 2026-03-04. The codebase is heavily workflow-oriented — 97% of LOC lives in
.github/workflows(YAML + Markdown), with a small but growing C# Unity codebase at 2,187 lines (24 scripts). The overall quality score is 25/100 ⬆️ (+7 from yesterday's 18), driven primarily by a recovery in comment density in the C# code (15.9%) following the recent enemy AI state machine implementation.The main area of concern remains the complete absence of automated tests — 0 test files and 0 test LOC in the C# source code. This alone caps the quality score at 70/100. The high code churn this week (72 commits, 39,000 source lines added) reflects rapid feature development in the Unity project, including enemy AI, collectibles, HUD, and player systems. Documentation coverage remains thin at just 1 doc file (1,123 LOC) for 145k total LOC.
📊 Visualizations
LOC Distribution by Language
YAML workflows dominate at 73.9% (107,703 LOC), followed by Markdown at 24.5% (35,668 LOC). C# source code represents only 1.5% but is the primary active development language. The ratio confirms this is a workflow-heavy project with a small Unity game core.
Top Directories by LOC
.github/workflowsaccounts for 96.8% of all LOC (140,997 lines), reflecting the agentic workflow infrastructure powering this project. Unity assets contribute 2,694 LOC and docs contribute 1,123 LOC.Quality Score Breakdown
The quality score improved to 25/100 today (⬆️ +7 from 18 yesterday). Test coverage remains the critical gap at 0/30 points — this single component blocks any possibility of a high score. Code organization scores 11/25, documentation 4/20, churn stability 4/15, and comment density 6/10.
Test Coverage Analysis
With 2,187 C# source lines and zero test lines, the project has a 0.00 test-to-source ratio against a recommended target of 0.50 (1,094 test LOC needed). As the Unity game grows rapidly (new enemy AI, collectibles, HUD, combat system all this week), adding tests becomes increasingly critical to prevent regressions.
Code Churn — Last 7 Days
The most-changed source files were dominated by new workflow definitions (
.mdfiles) and the updated PRD (docs/prd.md+1,113 lines). Source code churn totaled 39,000 lines added / 258 deleted across 220 files (excl. lock files). Lock file churn was 109,483 lines added — tracked separately to avoid inflating the quality score.Historical Trends (Last 6 Days)
Total LOC has grown from 143,591 → 145,649 (+1.4% over 6 days), driven by new workflow additions and Unity C# scripts. Quality score oscillated between 18–29, reflecting variability in comment density metric collection. Today's score of 25 represents stabilization after the 18 low on 2026-03-03.
📈 Detailed Metrics
Size Metrics
Lines of Code by Language
Lines of Code by Directory
Quality Indicators
Test Coverage
test_lines_of_code): 0 linestest_to_source_ratio): 0.00 ❌Code Churn (Last 7 Days)
Source Code Churn (Excludes *.lock.yml)
Most Active Source Files
docs/prd.md: +1,113 lines.github/workflows/daily-security-red-team.md: +836 lines.github/workflows/repo-audit-analyzer.md: +782 lines.github/workflows/daily-syntax-error-quality.md: +757 lines.github/workflows/daily-copilot-token-report.md: +733 lines.github/workflows/daily-cli-performance.md: +699 lines.github/workflows/daily-compiler-quality.md: +660 lines.github/workflows/prompt-clustering-analysis.md: +652 lines.github/workflows/agent-performance-analyzer.md: +645 lines.github/workflows/developer-docs-consolidator.md: +624 linesWorkflow Lock File Churn (*.lock.yml only)
Workflow Metrics
total_workflows): 85 filesDocumentation
prd.md)Quality Score: 25/100 ⬆️ (+7 from yesterday)
Component Breakdown
💡 Insights & Recommendations
🚨 Add Unit Tests (Critical) — The project has 0 test files against 2,187 C# LOC. The
PlayerCombat.cs,EnemyBase.cs, andPlayerHealth.csintroduced this week are ideal candidates for NUnit tests in Unity. Even 500 test LOC would unlock 10+ quality score points.📝 Expand Documentation — At 129.7:1 code-to-docs ratio, there's almost no developer documentation. Adding architecture docs and API docs for the new interfaces (
IDamageable,IEnemyState) would improve the score from 4/20 to 8+/20.🔧 Refactor Large Source Files —
PlayerCombat.cs(271 LOC) andPlayerHealth.cs(195 LOC) are growing rapidly. Consider splitting combat subsystems before they exceed 500 LOC.🎯 Consolidate Workflow Definitions — 85 workflow markdown files averaging 712 lines each is substantial maintenance surface. Review for opportunities to share common agent instructions via the existing shared import pattern.
📊 Instrument Comment Ratio — Comment ratio in C# improved to 15.9% (from near-zero yesterday) after the enemy AI work. Maintain this standard for all new C# files — add XML doc comments to public APIs for 8+/10 comment density score.
Report generated by Daily Code Metrics workflow — §22686373900
Historical data: 6 days | Last updated: 2026-03-04 19:52 UTC
References:
Beta Was this translation helpful? Give feedback.
All reactions