validate-tt-mlir-against-tt-xla

Automate cross-repo validation of tt-mlir pull requests against tt-xla CI.

295|145|Updated Jun 17, 2024
One-click install
npx skills add https://github.com/tenstorrent/tt-mlir --skill validate-tt-mlir-against-tt-xla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-tt-mlir-against-tt-xla
Source: https://github.com/tenstorrent/tt-mlir/tree/main/.claude/skills/validate-tt-mlir-against-tt-xla
Command: npx skills add https://github.com/tenstorrent/tt-mlir --skill validate-tt-mlir-against-tt-xla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-repo validation of tt-mlir pull requests against tt-xla CI is automated, enabling faster and safer integration testing.

Core Features & Use Cases

  • Automates uplift-based cross-repo validation by creating ephemeral branches and triggering CI tests across tt-mlir and tt-xla.
  • Identifies related branches, resolves uplift commits, and orchestrates cherry-picks to prepare CI runs.
  • Updates the PR with status blocks and dispatches tests for multiple suites as needed.

Quick Start

Submit a tt-mlir PR number to trigger an uplifted cross-repo validation against tt-xla CI.

Frequently Asked Questions about validate-tt-mlir-against-tt-xla

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

FAQPage Schema
How do I automate cross-repo validation for a tt-mlir pull request against tt-xla CI?

Cross-repo validation is automated by submitting a tt-mlir PR number, which creates an uplifted branch, cherry-picks commits, resolves the tt-xla branch, triggers CI workflows, and updates the PR with results.

What is uplift-based cross-repo validation between tt-mlir and tt-xla?

Uplift-based cross-repo validation creates ephemeral branches and triggers CI tests across tt-mlir and tt-xla to enable faster and safer integration testing.

Do I need special permissions to run cross-repo PR validation for tt-mlir and tt-xla?

Cross-repo PR validation requires access to both repositories and permissions to create and delete branches and dispatch workflows.

How does cross-repo CI validation prepare branches and trigger tests across tt-mlir and tt-xla?

Cross-repo CI validation identifies related branches, resolves uplift commits, orchestrates cherry-picks to prepare CI runs, and dispatches tests for multiple suites as needed.

Can I trigger multiple CI test suites when validating a tt-mlir pull request against tt-xla?

Validating a tt-mlir pull request against tt-xla dispatches tests for multiple suites as needed and updates the PR with status blocks.

What information do I need to start automated cross-repo validation for tt-mlir and tt-xla?

Automated cross-repo validation requires PR metadata such as the pull request number or URL to trigger the uplifted validation against tt-xla CI.