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

Files

T

gemini-cli[bot] 3eab0513cd # Proactive Improvement: Backlog Health & Stale Policy Optimization

## Overview
This PR addresses a significant growth in the repository's open issues (2342) and PRs (440) by optimizing the automated stale policy and adding visibility into backlog health.

## Changes
1. **New Metrics**:
    - `backlog_health.ts`: Tracks the median age (in days) of the 100 oldest open PRs and issues. This provides a "worst-case" signal for backlog stagnation.
    - `stale_ratio.ts`: Tracks the percentage of open items currently labeled as `stale`.
2. **Stale Policy Optimization**:
    - Increased `operations-per-run` in `.github/workflows/stale.yml` from default (~30) to 500 total (300 for issues, 200 for PRs).
    - Split the stale job into two parallel jobs (`stale-issues` and `stale-prs`) to increase daily throughput and prevent issues from blocking PR processing.

## Rationale
Metrics analysis showed that while the repository has excellent "Fast Path" performance (PRs merged in ~23 hours), it has a massive "Slow Path" backlog that is likely not being touched by automation due to default throttling in `actions/stale`. By increasing the processing limit, we can accelerate the cleanup of stale items and help maintainers focus on active work.

## Impact
- **Productivity**: Reduces "noise" in the issue tracker and PR list.
- **Observability**: New metrics will allow the "Bot Brain" to monitor the effectiveness of these policy changes over time.
- **Latency**: Expected to decrease the median age of open items as stale ones are closed.

2026-04-30 23:35:05 +00:00

brain

Fix posting invalid response to a comment (#26266 )

2026-04-30 18:22:59 +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

# Proactive Improvement: Backlog Health & Stale Policy Optimization

2026-04-30 23:35: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.