eval-harness

Define and run capability and regression evals for Gemini Code sessions.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/riftzen-bit/gemini-setup --skill eval-harness-riftzen-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-harness
Source: https://github.com/riftzen-bit/gemini-setup/tree/main/skills/eval-harness
Command: npx skills add https://github.com/riftzen-bit/gemini-setup --skill eval-harness-riftzen-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The eval-harness provides a formal, repeatable framework for defining, running, and reporting evaluations for Gemini Code sessions so teams can quantify AI behavior, prevent regressions, and gate releases on objective metrics.

Core Features & Use Cases

  • Eval-Driven Development: Define capability and regression evals before implementation to set clear success criteria.
  • Multiple Grader Types: Support deterministic code graders, model-based graders for open-ended outputs, and human review flags for high-risk changes.
  • Metrics & Reporting: Record pass@k and pass^k statistics, store eval definitions and run histories, and generate eval reports for release decisions.
  • Integration Patterns: Create eval artifacts in .gemini/evals, run checks during implementation, and generate consolidated reports for CI and release notes.
  • Use Case Example: Add an authentication feature with pre-defined capability checks, run graders to verify behavior, and use pass@k thresholds to decide readiness.

Quick Start

Define an eval for add-authentication, run the eval check to execute graders, and generate the eval report to review pass@k metrics.

Frequently Asked Questions about eval-harness

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

FAQPage Schema
What is eval-driven development for AI code generation?

Eval-driven development defines capability and regression evaluations before implementation to set clear success criteria. It quantifies AI behavior and prevents regressions by applying deterministic code graders and model-based graders to Gemini Code sessions.

How do I measure pass@k metrics for AI-assisted development workflows?

You measure pass@k metrics by running formal evaluations with deterministic and probabilistic graders on Gemini Code sessions. The framework records pass@k and pass^k statistics, stores run histories, and generates reports for release decisions.

How do I set up regression testing for Gemini Code sessions?

Set up regression testing by creating eval artifacts in the .gemini/evals directory, defining capability and regression evals, and running eval checks during implementation. This applies deterministic and model graders to verify behavior and prevent regressions.

Can I use model graders for open-ended AI code outputs?

Yes, model graders support evaluating open-ended outputs alongside deterministic code graders. The framework integrates model-based probabilistic graders and human review flags for high-risk changes to quantify AI behavior accurately.

Does eval-harness work with CI pipelines for release gating?

Yes, it provides integration commands for CI and developer workflows. You can run checks during implementation, generate consolidated eval reports, and use pass@k thresholds to gate releases and decide feature readiness.

What's the best way to prevent AI code regressions across release cycles?

The best way is implementing formal eval-driven development with pre-defined capability checks. Run deterministic and model graders to verify behavior, record pass@k statistics, and use threshold metrics to gate releases and prevent regressions.