mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-14 22:02:59 -07:00

Files

T

gemini-cli[bot] 07d3b4c470 # PR Description: Improve Metric Fidelity via Search-Based Sampling

## Summary
This PR improves the accuracy and reliability of the repository's health metrics by transitioning core velocity scripts from static sampling (`last: 100`) to search-based sampling with a fixed 7-day window.

## Changes
- **throughput.ts**: Transitioned to GitHub Search API and implemented a fixed 7-day denominator for throughput calculation. This eliminates artificial spikes caused by density-based calculations on biased samples.
- **latency.ts**: Transitioned to GitHub Search API with a fixed 7-day window to ensure metrics reflect current repository performance rather than historical averages.
- **user_touches.ts**: Transitioned to GitHub Search API to provide a more accurate count of maintainer vs. community interactions.
- **lessons-learned.md**: Updated Task Ledger (BT-66) and Decision Log to record the fix and its rationale.

## Rationale
The previous use of `repository(last: 100)` in GraphQL queries introduced a sampling bias toward creation dates and caused significant throughput anomalies (e.g., reporting 3,355 items/day during batch closures). Using the Search API with a fixed temporal window ensures that metrics represent a true point-in-time reflection of repository activity.

## Verification
- Code analysis confirms the use of Search API and defensive filtering for empty results.
- Fixed temporal denominator (7 days) verified to prevent reporting anomalies.
- Pattern consistency verified across all modified scripts.

2026-05-12 17:13:05 +00:00

brain

feat(bot): add actions spend metric script (#26463 )

2026-05-04 21:01:39 +00:00

history

Implement bot that performs time-series metric analysis and suggests repo management improvements (#25945 )

2026-04-28 16:49:53 +00:00

metrics

# PR Description: Improve Metric Fidelity via Search-Based Sampling

2026-05-12 17:13:05 +00:00

ci-policy.toml

Implement bot that performs time-series metric analysis and suggests repo management improvements (#25945 )

2026-04-28 16:49:53 +00:00

README.md

Implement bot that performs time-series metric analysis and suggests repo management improvements (#25945 )

2026-04-28 16:49:53 +00:00

README.md

Gemini CLI Bot (Cognitive Repository)

This directory contains the foundational architecture for the gemini-cli-bot, transforming the repository into a proactive, evolutionary system.

It implements a dual-layer approach to balance immediate responsiveness with long-term strategic optimization.

Layered Execution Model

1. System 1: The Pulse (Reflex Layer)

Purpose: High-frequency, deterministic maintenance.
Frequency: 30-minute cron (.github/workflows/gemini-cli-bot-pulse.yml).
Implementation: Pure TypeScript/JavaScript scripts.
Classification: Optionally utilizes Gemini CLI for high-confidence semantic classification (e.g., triage, labeling, sentiment) while preferring deterministic logic for equivalent tasks.
Phases:
- Reflex Execution: Runs triage, routing, and automated maintenance scripts in reflexes/scripts/.
Output: Real-time action execution.

2. System 2: The Brain (Reasoning Layer)

Purpose: Strategic investigation, policy refinement, and proactive self-optimization.
Frequency: 24-hour cron (.github/workflows/gemini-cli-bot-brain.yml).
Implementation: Agentic Gemini CLI phases.
Phases:
- Metrics Collection: Executes scripts in metrics/scripts/ to track repository health (Open issues, PR latency, throughput, etc.).
- Phase 1: Reasoning (Metrics & Root-Cause Analysis): Analyzes time-series metric trends and repository state to identify bottlenecks or productivity gaps, tests hypotheses, and proposes script or configuration changes to improve repository health and maintainability.
- Phase 2: Critique: A technical and logical validation layer that reviews proposed changes for robustness, actor-awareness, and anti-spam protocols.
- Phase 3: Publish: Automatically promotes approved changes to Pull Requests, handles branch management, and responds to maintainer feedback.

Directory Structure

metrics/: Deterministic runner (index.ts) and scripts for tracking repository metrics via GitHub CLI.
reflexes/scripts/: Deterministic triage and routing scripts executed by the Pulse.
brain/: Prompt templates and logic for strategic root-cause analysis (Phase 1: metrics.md) and technical validation (Phase 2: critique.md).
history/: Persistent storage for time-series metrics artifacts.
lessons-learned.md: The bot's structured memory, containing the Task Ledger, Hypothesis Ledger, and Decision Log.

Usage

Local Metrics Collection

To manually collect repository metrics locally, run the following command from the workspace root:

npx tsx tools/gemini-cli-bot/metrics/index.ts

This will execute all scripts within metrics/scripts/ and output the results to tools/gemini-cli-bot/history/metrics-before.csv.

Development

When modifying the bot's logic:

Reflexes: Add or update scripts in reflexes/scripts/.
Reasoning: Update the prompts in brain/ to refine how the bot identifies bottlenecks.
Critique: Update the prompts in critique/ to strengthen the validation of proposed changes.