MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-15 06:12:50 -07:00
Code Issues Packages Projects Releases Wiki Activity

Rename processes to reflexes.

Browse Source
This commit is contained in:
Christian Gunderman
2026-04-24 14:20:34 -07:00
parent 2e1ef0ee2c
commit 4512d9a8a1
2 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/gemini-cli-bot/README.md
+3 -4
View File
@@ -31,10 +31,9 @@ long-term strategic optimization.
- `metrics/`: Contains the deterministic runner (`index.ts`) and individual
TypeScript scripts (`scripts/`) that use the GitHub CLI to track metrics like
open issues, PR latency, throughput, and reviewer domain expertise.
- `processes/scripts/`: Placeholder directory for future deterministic triage
and routing scripts.
- `investigations/`: Placeholder directory for agentic root-cause analysis
phases.
- `reflexes/scripts/`: Placeholder directory for future deterministic triage and
routing scripts.
- `brain/`: Placeholder directory for the Brain's root-cause analysis phases.
- `critique/`: Placeholder directory for policy evaluation.
- `history/`: Storage for downloaded metrics artifacts from previous runs.
tools/gemini-cli-bot/investigations/metrics_analysis.md → tools/gemini-cli-bot/brain/metrics.md
+4 -4
View File
@@ -1,4 +1,4 @@
# Phase: Metrics Investigation & Root-Cause Analysis
# Phase: The Brain (Metrics & Root-Cause Analysis)
## Goal
@@ -55,14 +55,14 @@ For each metric not meeting goals or showing a negative trend:
### 3. Maintainer Workload Assessment
Before blaming or proposing processes that rely on maintainer action (e.g., more
Before blaming or proposing reflexes that rely on maintainer action (e.g., more
triage, more reviews):
- **Quantify Capacity**: Assess the volume of open, unactioned work (untriaged
issues, review requests) against the number of active maintainers.
- If the ratio indicates overload, **do not propose solutions that simply
generate more pings**. Instead, prioritize systemic triage, automated routing,
or auto-closure processes.
or auto-closure reflexes.
### 4. Actor-Aware Bottleneck Identification
@@ -76,7 +76,7 @@ Before proposing an intervention, accurately identify the blocker:
### 5. Policy Critique & Evaluation
- **Review Existing Policies**: Examine the existing automation in
`.github/workflows/` and scripts in `tools/gemini-cli-bot/processes/scripts/`.
`.github/workflows/` and scripts in `tools/gemini-cli-bot/reflexes/scripts/`.
- **Analyze Effectiveness**: Based on your metrics analysis, determine if
current policies are achieving their goals (e.g., Is triage reducing latency?
Are stale issues closed as expected?).