gemini-cli/tools/optimizer/investigations/INVESTIGATIONS.md

Optimizer Investigations

This document contains findings from the analysis of project metrics, focusing on issues, PRs, and general project health.

1. Metrics Overview

The current metrics baseline (metrics-before.csv) is as follows:

• Completed Community PRs: 1136
• Open Community PRs: 336 (Note: Total open PRs fetched via script is 486)
• Open Issues: 1000
• PR Latency: 40.84
• Test Flakiness: 374

Historical Comparison: There were no historical metrics in the history/ directory to compare against, so we cannot determine if these are improving or worsening over time.

2. Issues Analysis

We ran a script to analyze issue labels, and we developed two additional scripts (investigate_age.cjs and investigate_assignees.cjs) to extract more data.

Key Findings:

• Triage Bottleneck: A significant majority of issues (609 out of 1000) have the status/need-triage label.
• Unassigned Issues: An overwhelming 85.6% of open issues (856 out of 1000) are UNASSIGNED. This indicates a major gap in routing or taking ownership of issues.
• Age Distribution:
  • < 1 week: 128
  • 1-4 weeks: 488
  • 1-3 months: 384
  • > 3 months: 0 (in our sampled batch)
  • Most issues sit open for 1 to 12 weeks. The lack of assignment and triage likely contributes to issues stagnating in the 1-4 weeks and 1-3 months buckets.
• Common Areas: The most affected areas are area/agent (338) and area/core (271).

3. Pull Requests Analysis

We analyzed open PRs using the existing investigate_prs.cjs script and our new age distribution script.

Key Findings:

• Needs Help/Issues: A large chunk of PRs are labeled help wanted (204) and status/need-issue (86).
• Age Distribution:
  • < 1 week: 71
  • 1-4 weeks: 222
  • 1-3 months: 193
  • PR age correlates closely with the reported high pr_latency (40.84). Like issues, most PRs are languishing in the 1 to 12 weeks range without resolution.
• Common Areas: area/core represents the largest subset of PRs (215).

4. Conclusion

The metrics suggest that the project has a significant backlog and high latency. The primary contributors seem to be:

1. Lack of Triage & Assignment: Issues are opened but not assigned, leaving them in a need-triage state for weeks to months.
2. PR Stagnation: Many PRs are open and likely lacking review, leading to a build-up in the 1-4 week and 1-3 month buckets. The help wanted and status/need-issue labels suggest many PRs might be incomplete or lacking context, which slows down the review process.