warp-fork

Fork a warp route from a local HTTP registry in the background.

72|602|Updated Dec 13, 2021
One-click install
npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill warp-fork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: warp-fork
Source: https://github.com/hyperlane-xyz/hyperlane-monorepo/tree/main/.claude/skills/warp-fork
Command: npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill warp-fork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to fork warp routes from a local HTTP registry to simulate transactions on a set of anvil forks, enabling isolated development and testing.

Core Features & Use Cases

  • Local Warp Route Forking: Fork a warp route from the local HTTP registry for testing and development.
  • Background Execution: Run the fork in the background so it doesn't block the conversation.
  • Prompted Warp Route Selection: Prompt for warp route identifier to guide the fork process and handle unavailable routes gracefully.

Quick Start

Use a registry URL (default http://localhost:3333) and a warp route ID to fork: pnpm -C typescript/cli exec tsx cli.ts warp fork --registry http://localhost:3333 --warpRouteId $WARP_ROUTE_ID

Frequently Asked Questions about warp-fork

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

FAQPage Schema
How do I fork a warp route locally for development testing?

To fork a warp route locally, use the warp fork command with pnpm and tsx, providing your warp route ID and local registry URL. This simulates transactions on anvil forks for isolated development without blocking your conversation.

What is a local warp route fork used for?

A local warp route fork is used to simulate transactions on anvil forks, enabling isolated development and testing. It allows developers to safely test warp route behavior away from production environments.

Do I need a local registry running to fork a warp route?

Yes, you need a local HTTP registry running at port 3333. The fork process requires this local registry to fetch the warp route configuration before executing the background simulation.

Can I run a warp fork in the background without blocking my terminal?

Yes, the warp fork executes in the background so it does not block your conversation. It reports the background shell ID, which you can use later to terminate the process when testing is complete.

What happens if I specify a warp route ID that is unavailable?

If you specify an unavailable warp route ID, the fork process handles the unavailable route gracefully. It prompts for a valid warp route identifier to guide the fork process and prevent hard failures.

Why use anvil forks when testing warp routes?

Using anvil forks allows you to simulate transactions against a copy of the blockchain state locally. This provides an isolated environment for testing warp route behavior safely without risking actual assets or network state.