Stop the background HTTP registry server started by /start-http-registry — TaskStop / KillShell by the recorded task ID, plus a /proc cmdline-scan fallback for minimal-tool sandboxes with no ps/lsof/pkill/fuser. Referenced by every warp deploy/update skill that starts the registry.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Stop the background HTTP registry started via /start-http-registry. Always stop it at the end of the skill — even on failure paths — so no background process is left running.
Primary: TaskStop (or KillShell) with the task/shell ID recorded when the registry was started.
Fallback (minimal-tool sandboxes): if TaskStop doesn't clean up the underlying process and ps / lsof / pkill / fuser aren't available, scan /proc for the registry's cmdline and kill it:
# Find PIDs matching the registry process — exclude the scanning shell itself
SELF_PID=$$
for pid in $(ls /proc | grep -E '^[0-9]+$'); do
[ "$pid" = "$SELF_PID" ] && continue
if grep -aql 'http-registry-server\|start:http-registry' /proc/$pid/cmdline 2>/dev/null; then
echo "killing http-registry pid=$pid"
kill "$pid" 2>/dev/null || true
fi
done
Always run the fallback after TaskStop regardless — it is idempotent if the process is already gone.
/warp-deploy-init-route, /warp-deploy-update-owners, /warp-update, /warp-update-extend, /warp-update-resolve-artifacts — every skill that starts the HTTP registry.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.