跳到正文
cccskills
免费在 GitHub 公开

warp-deploy-nexus

Add a new warp route to the Nexus UI whitelist. Checks out the nexus branch of hyperlane-warp-ui-template, adds the warp route ID to warpRouteWhitelist.ts, and opens a PR targeting the nexus branch.

中文简介正在准备中。当前显示原文说明。

集成工具LinearGitHub

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Warp Deploy — Nexus Whitelist

You are adding a warp route to the Nexus UI whitelist.

Input

The user provides:

  • One or more warp route IDs (e.g. SOL/igra) and/or Linear ticket URL(s)

If Linear ticket URL(s) are provided, fetch each ticket to extract the warp route ID. If neither is provided, ask for them now.

When multiple routes are provided, add all of them in a single PR (Steps 3–5 cover all routes at once).


Step 1: Confirm the warp route ID(s)

Show the user the warp route IDs you'll add, then end your message with this marker (this MUST be the very last thing in your message):

[CONFIRM: Add warp route IDs <ids> to Nexus whitelist]

Note: [CONFIRM: ...] is a Haggis-specific harness primitive — Haggis renders it as an inline approve/reject button. In other coding-assistant contexts it is just text.


Step 2: Prepare the branch

The hyperlane-warp-ui-template repo is at the same level as hyperlane-monorepo:

REPO_PATH="$(pwd)/../hyperlane-warp-ui-template"
  1. Ensure the repo is clean and up to date on the nexus branch:
cd "$REPO_PATH"
git fetch origin
git checkout nexus
git pull origin nexus
  1. Create a new branch from nexus. For a single route use feat/<warp-route-id-slugified> (lowercase, / → -). For multiple routes use a descriptive slug like feat/add-<token>-igra-routes:
git checkout -b feat/<slug>

Step 3: Add to whitelist

The whitelist file is at:

$REPO_PATH/src/consts/warpRouteWhitelist.ts

Read the file and add the warp route ID to the warpRouteWhitelist array. Insert it in alphabetical order by token symbol, then by chain string. Preserve existing formatting (single quotes, trailing comma on each entry).

Example — adding SOL/igra to an existing list:

export const warpRouteWhitelist: Array<string> | null = [
  'SOL/igra',
  'USDC/mainnet-cctp-v2-fast',
];

Step 3b: Verify the edit compiles

Before committing, run the repo's TypeScript type-check to catch any syntax slip (trailing comma, mis-quoted string, etc.) that would ship a broken Nexus build:

cd "$REPO_PATH"
pnpm typecheck

(The typecheck script is defined in package.json as tsc.)

If pnpm typecheck reports any error from src/consts/warpRouteWhitelist.ts, stop — surface the error, do not commit. The most common cause is a stray comma or a non-string array entry; re-read the file, fix, and re-run until clean.


Step 4: Commit and push

cd "$REPO_PATH"
git add src/consts/warpRouteWhitelist.ts
git commit -m "feat: add <WARP_ROUTE_ID(s)> to Nexus whitelist"
git push origin <branch-name>

For multiple routes, list them all in the commit message: feat: add USDS, WETH, USDT igra routes to Nexus whitelist.


Step 5: Open a PR

Target branch is nexus (not main).

For a single route:

gh pr create \
  --base nexus \
  --title "feat: add <WARP_ROUTE_ID> to Nexus whitelist" \
  --body "$(cat <<'EOF'
Adds `<WARP_ROUTE_ID>` to the Nexus UI warp route whitelist.

| Field | Value |
| ----- | ----- |
| **Linear** | [<TICKET_ID>](<LINEAR_URL>) |
| **Warp route** | `<WARP_ROUTE_ID>` |
EOF
)"

For multiple routes, list each route ID in the body. Combine all Linear ticket links in one row (comma-separated):

gh pr create \
  --base nexus \
  --title "feat: add <token> igra warp routes to Nexus whitelist" \
  --body "$(cat <<'EOF'
Adds the following warp routes to the Nexus UI whitelist:

| Field | Value |
| ----- | ----- |
| **Linear** | [<TICKET_ID_1>](<LINEAR_URL_1>) · [<TICKET_ID_2>](<LINEAR_URL_2>) · [<TICKET_ID_3>](<LINEAR_URL_3>) |

- `<WARP_ROUTE_ID_1>`
- `<WARP_ROUTE_ID_2>`
- `<WARP_ROUTE_ID_3>`
EOF
)"

Show the user the PR URL when done.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.

中文简介正在准备中。当前显示原文说明。

hyperlane-xyz/hyperlane-monorepo762026年10月23日 更新

查看 hyperlane-xyz 的全部技能

报告此技能的问题