Daily Code Metrics Report - 2026-03-02 #121
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-05T19:54:06.843Z.
|
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 maintains 144,540 total LOC across 247 files, with a quality score of 22/100 — consistent with the previous two days. The codebase is dominated by YAML lock files (74.4%) and Markdown workflow definitions (24.7%), reflecting an agentics-heavy repository structure. The most notable concern remains the complete absence of automated tests and a very low documentation ratio.
Source code churn (excluding generated
*.lock.ymlfiles) shows 185 files modified across 53 commits in the last 7 days with +37,370/-217 lines, indicating active workflow development. The primary areas of change are workflow.mddefinitions and thedocs/prd.mdfile. Churn stability remains at 3/15 due to the high number of modified files relative to total files (75%).📊 Visualizations
LOC Distribution by Language
YAML lock files dominate at 107,491 LOC (74.4%), followed by Markdown at 35,668 LOC (24.7%). This is expected for an agentics workflow repository where compiled lock files represent workflow infrastructure.
Top Directories by LOC
.github/workflows(lock) accounts for 74.4% of all LOC, followed by workflow source.mdfiles at 23.0%. The Unity directory (1,502 LOC) and docs (1,123 LOC) represent the non-infrastructure codebase.Quality Score Breakdown
The quality score of 22/100 is driven down primarily by zero test coverage (0/30) and low documentation coverage (4/20). Code organization (10/25) is impacted by 105 files exceeding 500 LOC — mostly generated lock files.
Test Coverage Analysis
No test files detected in the repository. With 144,540 LOC of source material, a target of 72,270+ test LOC would be needed to reach a 0.5 test-to-source ratio. Adding any tests would immediately improve the quality score.
Code Churn (Last 7 Days)
The most active source file is
docs/prd.md(+1,126/-3 lines), followed by multiple new workflow.mddefinitions being added. All top changed files show additions-only or near-zero deletions, indicating primarily additive development.Historical Trends (4 Days)
Total LOC has been stable at ~144,540 for the past 3 days (up from 143,591 on Feb 27). Quality score dropped from 29 → 22 between Feb 27 and Feb 28 and has held steady since. Comment ratio improved from 0% → 3.9% over the tracked period.
📈 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.00Code Churn (Last 7 Days)
Source Code Churn (Excludes *.lock.yml)
Most Active Source Files
docs/prd.md: +1,126/-3 lines.github/workflows/daily-security-red-team.md: +836/0 lines.github/workflows/repo-audit-analyzer.md: +782/0 lines.github/workflows/daily-syntax-error-quality.md: +757/0 lines.github/workflows/daily-copilot-token-report.md: +733/0 lines.github/workflows/daily-cli-performance.md: +699/0 lines.github/workflows/daily-compiler-quality.md: +660/0 lines.github/workflows/prompt-clustering-analysis.md: +652/0 lines.github/workflows/agent-performance-analyzer.md: +645/0 lines.github/workflows/developer-docs-consolidator.md: +624/0 linesWorkflow Lock File Churn (*.lock.yml only)
Note: Lock file churn is reported separately and excluded from quality score calculations to avoid noise from generated files.
Workflow Metrics
total_workflows): 113 filesDocumentation
Quality Score: 22/100
Component Breakdown
💡 Insights & Recommendations
🔴 Add Tests: Zero test coverage is the single largest drag on quality score. Even a small test suite targeting Unity C# scripts or workflow validation would immediately improve the 0/30 test score. Target
test_to_source_ratio≥ 0.1 as a first milestone.🟡 Expand Documentation: The
docs/prd.mdis the only documentation file for a 144K LOC codebase. Adding documentation for the Unity project, key workflows, and onboarding guides would improve the 4/20 documentation score.🟡 Reduce Lock File Noise: With 85 lock.yml files comprising 74% of codebase LOC, consider reviewing the lock file retention policy. Compiled workflow files inflate metrics and reduce code organization scores.
🟢 Monitor Churn Trends: The high source code churn (185/247 files in 7 days) is expected during active development but should be watched. A stabilization period would improve the churn stability score from 3/15 toward 10+/15.
🟢 Comment Coverage: Comment ratio improved from 0% to 3.9% — good progress. Continue adding meaningful comments to YAML workflows to reach the 8-10% target for full comment density points.
Report generated by Daily Code Metrics workflow • §22592885452
Historical data: 4 days tracked | Last updated: 2026-03-02 19:49 UTC
Beta Was this translation helpful? Give feedback.
All reactions