feat(evals): add eval coverage report command

[ved015]

Summary

Adds an eval:coverage command that reports eval coverage for built-in tools by cross-referencing eval inventory tool references with the tool registry.

Details

• Wires npm run eval:coverage to a new scripts/eval-coverage-cli.ts entry point.
• Adds --root support for running coverage against a specific repo path.
• Computes covered and uncovered tools, including case counts, per-file policy distribution, aliases, diagnostics, and coverage percentage.
• Formats a human-readable report with covered tools and uncovered tools grouped by category.

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new CLI tool to track and report evaluation coverage for built-in tools. By analyzing the existing evaluation inventory and comparing it against the tool registry, the new command provides developers with insights into which tools are covered by evaluations, how many cases exist per tool, and any relevant diagnostic information. This addition improves visibility into the test suite's effectiveness and helps identify gaps in tool coverage.

Highlights

• New CLI Command: Added a new eval:coverage command to package.json to generate evaluation coverage reports.
• Coverage Logic: Implemented core logic in scripts/utils/eval-coverage.ts to cross-reference tool usage in evaluations against the tool registry.
• CLI Entry Point: Created scripts/eval-coverage-cli.ts to handle command-line arguments, including optional root path specification, and output the generated report.
• Testing: Added comprehensive unit and integration tests in scripts/tests/eval-coverage.test.ts to verify coverage calculations, report formatting, and real-world directory processing.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

📊 PR Size: size/L

• Lines changed: 856
• Additions: +856
• Deletions: -0
• Files changed: 4

[gemini-code-assist]

Code Review

This pull request introduces an evaluation coverage reporting tool, adding a new CLI script (scripts/eval-coverage-cli.ts), a utility module (scripts/utils/eval-coverage.ts), associated unit tests, and a new npm script eval:coverage in package.json. The reviewer identified a potential runtime crash (TypeError) in the coverage reporting utility if a tool's category is undefined, and provided a code suggestion to safely default undefined categories to 'unknown'.