E2e To Bazel

google/e2e-to-bazel

>- Converts end-to-end (e2e) test targets or paths to `bazel run` commands for `heir-opt`. Use when you need to convert an e2e test target (where flags are defined in the BUILD file) to a shell command whose flags can be modified for further analysis and debugging.

393 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

754

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/google/heir --skill e2e-to-bazel

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

5 sections, as written by the author

E2E To Bazel

Overview

This skill guides the agent in using the e2e_to_bazel tool to convert e2e test

targets or paths to executable commands.

Usage

Converting a Test Target or Path

To convert an e2e test target, directory, or source file to a bazel run

command, use the following command recipes:

bazel run //third_party/heir/scripts:e2e_to_bazel -- {target_or_path}

Replace {target_or_path} with the test target (e.g.,

//tests/Examples/lattigo/ckks/mnist:mnist_test), directory, or source file

path.

Gotchas

Blaze Query Dependency: The tool relies on bazel query to extract

attributes. This requires a working blaze environment and may be slow for

the first run.

Workspace State: It requires that the workspace is in a state where

bazel query can evaluate the targets.

Source file mapping: If a source file is provided, it searches for

heir_opt targets that depend on it.

Copy this checklist and track progress:

- [ ] Step 1: Identify the e2e test target, directory, or file to convert.
- [ ] Step 2: Run the `e2e_to_bazel` tool on it.
- [ ] Step 3: Inspect the generated command or run it.
- [ ] Step 4: Verify execution results.

How to use it

Copy the folder

Take google/e2e-to-bazel from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.