Lit To Bazel Agent Skill
>- Converts MLIR lit test files to `bazel run` commands. Use when you need to convert a failing MLIR lit test target (containing RUN lines) to a shell command whose flags can be modified for further analysis and debugging.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/google/heir --skill lit-to-bazelThe instruction itself
5 sections, as written by the authorLit To Bazel
Overview
This skill guides the agent in using the lit_to_bazel tool to convert MLIR
test files to executable commands.
Usage
Converting a Test File
To convert a lit test file to a bazel run command, use the following command
recipes:
bazel run //third_party/heir/scripts:lit_to_bazel -- {test_file_path}
Replace {test_file_path} with the absolute path to the test file. The absolute
path is necessary because the bazel run command runs relative to its runfiles
directory, and so a relative path will not be relative to the VCS root of the
project.
Gotchas
- Absolute Paths: The tool replaces
%sin RUN lines with the absolute path
of the test file to ensure it works in the sandbox.
- Piped RUN commands: The tool supports piped RUN lines, such as piping
heir-opt into heir-translate.
- Complex RUN commands: Some very complex RUN lines are not supported, such
as lit test files with multiple RUN lines that interact via writing to and
reading from temporary files. When encountering situations like this, you
should stop and warn the user.
- Non-lit tests: Some test targets are not lit tests, and these do not need
the lit_to_bazel tool.
Copy this checklist and track progress:
- [ ] Step 1: Identify the test file to convert.
- [ ] Step 2: Run the `lit_to_bazel` tool on the file.
- [ ] Step 3: Inspect the generated command or run it.
- [ ] Step 4: Verify execution results.
<!-- mdformat global-off -->
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take google/lit-to-bazel from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.