shepherd-emule-pr

Review and locally rebase tt-emule pull requests with JIT compile-probes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the unreliability of automated PR reviews by enforcing strict adherence to the tt-emule ethos, ensuring that code changes are faithful to silicon implementations and free of divergent duplicates or JIT-compile errors.

Core Features & Use Cases

  • Ethos-Driven Review: Validates PRs against specific emule bug classes like dangling symbols, ODR violations, and silent silicon divergences.
  • Build-Based Verification: Uses targeted JIT compile-probes to catch errors in seconds without requiring a full regression suite.
  • Safe Handoff: Performs local rebasing and generates a comprehensive verification summary, keeping the human developer in the loop for final pushes.

Quick Start

Invoke the shepherd-emule-pr skill to review and prepare the open pull request number 240 for merging into the main branch.

Frequently Asked Questions about shepherd-emule-pr

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

FAQPage Schema
How do I automate code review for tt-emule pull requests?

Automating code review for tt-emule pull requests involves validating changes against silicon-faithful implementation standards, probing JIT-compile integrity, and detecting ODR violations or dangling symbols.

How does targeted JIT compile-probing work for emulation PRs?

Targeted JIT compile-probing catches header compile errors in seconds without a full regression suite by selectively compiling specific headers affected by the pull request.

Can I use this to rebase local branches before merging feature PRs?

Yes, you can use this to rebase local branches before merging feature PRs, as it performs local branch synchronization and generates a comprehensive verification summary for safe handoff.

What is the best way to verify silicon-faithful implementation in emulation code?

The best way to verify silicon-faithful implementation in emulation code is ethos-driven review that detects silent silicon divergences and divergent duplicates before merging changes.

Why does automated PR review fail to catch silent silicon divergences?

Automated PR review fails to catch silent silicon divergences without strict ethos enforcement that specifically validates code changes against actual silicon implementations and known emule bug classes.