uplift

Bisect tt-metal and tt-umd dependency updates to isolate C++ and JIT regressions.

4|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/tenstorrent/tt-emule --skill uplift-tenstorrent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uplift
Source: https://github.com/tenstorrent/tt-emule/tree/main/.claude/skills/uplift
Command: npx skills add https://github.com/tenstorrent/tt-emule --skill uplift-tenstorrent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves complex software regressions that occur when updating the tt-metal and tt-umd dependencies, ensuring that the emule runtime remains stable and functional after upstream changes.

Core Features & Use Cases

  • Regression Isolation: Provides a structured methodology to bisect and identify whether a failure originates from the tt-metal source or the bundled tt-umd submodule.
  • Fix Verification: Guides the user through creating a deterministic oracle to prove the root cause and validate the effectiveness of the fix.
  • Use Case: When a pin bump causes device-open crashes or JIT-compile errors, use this Skill to systematically isolate the culprit and apply a faithful, minimal fix to the emule shim layer.

Quick Start

Invoke the uplift skill to begin a systematic bisection of the current tt-metal and tt-umd pin bump regression.

Frequently Asked Questions about uplift

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

FAQPage Schema
How do I fix tt-metal dependency update regressions in the emule runtime?

Isolate tt-metal regression causes by bisecting upstream commits to verify the boundary between tt-metal source changes and emule-side shims, creating a deterministic oracle to prove the root cause before applying a minimal fix.

What is the best way to debug C++ build failures and JIT-compile errors after a tt-metal pin bump?

Debugging C++ build failures and JIT-compile errors after a tt-metal pin bump requires a systematic bisection approach to identify the specific commit responsible for the regression and verify the fix using a deterministic oracle.

Why does my emule runtime hang or crash on device-open after updating tt-umd?

Device-open crashes occur when tt-umd updates introduce regressions in the emule runtime. Use a structured bisection methodology to isolate the culprit commit in the bundled submodule and verify the root cause with a deterministic oracle.

Can I isolate tt-metal source failures from tt-umd submodule failures during regression bisection?

Yes, you can isolate tt-metal source failures from tt-umd submodule failures by using a systematic bisection approach that verifies the boundary between upstream changes and emule-side shims to pinpoint the exact origin of the regression.

How do I verify a tt-metal regression fix before merging the emule shim update?

Verify a tt-metal regression fix by creating a deterministic oracle that proves the root cause of the C++ build failure or runtime hang, ensuring the minimal fix applied to the emule shim layer is effective and faithful to the original behavior.