eval-harness

Automate eval-driven testing workflows for Gemini CLI sessions with deterministic graders.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill eval-harness-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-harness
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/eval-harness
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill eval-harness-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes and automates eval-driven testing to ensure Gemini CLI sessions behave as intended across changes.

Core Features & Use Cases

  • Capability and Regression Evals definitions to codify expectations
  • Deterministic and model-based graders to assess changes
  • Evaluation report generation with pass/fail metrics and baselines

Quick Start

Run an eval workflow to validate Gemini CLI changes end-to-end.

Frequently Asked Questions about eval-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate eval-driven testing for Gemini CLI sessions?▼

Automate eval workflows for Gemini CLI by defining capability and regression evals, running deterministic or model-based graders, and generating evaluation reports with pass@k metrics across code changes.

What is eval-driven testing and how does it ensure software quality in CLI tools?▼

Eval-driven testing formalizes software quality by codifying capability expectations into eval definitions, running graders against changes, and comparing pass@k metrics against baselines to catch regressions in CLI behavior.

Can I use model-based graders alongside human reviews for Gemini CLI regression testing?▼

Yes, Gemini CLI regression testing supports code-based graders, model-based graders, and human reviews simultaneously to assess changes and generate comprehensive evaluation reports.

Where should eval definitions be stored for Gemini CLI testing workflows?▼

Eval definitions for Gemini CLI testing workflows should be stored under the .gemini/evals directory to maintain structure and ensure consistent evaluation report generation across code changes.

Does Gemini CLI testing support pass@k metrics and baseline comparisons for code changes?▼

Yes, Gemini CLI testing outputs pass@k metrics and tracks baselines in evaluation reports, allowing you to measure reliability and detect regressions when evaluating code changes end-to-end.

What is the best way to set up regression evals for Gemini CLI development?▼

Set up regression evals for Gemini CLI development by defining capability expectations in .gemini/evals, configuring deterministic graders, and running automated workflows to validate changes end-to-end before deployment.