Skip to content

hyperlane-xyz/hyperlane-monorepo / .agents/skills/build-docker-image

build-docker-image

Verified

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.

Trigger Docker Image Builds

Build and publish Docker images to GHCR (ghcr.io/hyperlane-xyz/*).

Workflows

WorkflowImage(s)Contents
rust-docker.ymlhyperlane-agentRust relayer, validator, scraper
monorepo-docker.ymlhyperlane-monorepoFull TS/Solidity monorepo
node-services-docker.ymlhyperlane-node-servicesAll TS node services (rebalancer, warp-monitor, ccip-server, keyfunder, relayer)

How to Trigger

Use gh workflow run with --ref to specify the branch, tag, or commit:

# Agent image (Rust)
gh workflow run rust-docker.yml --ref <branch>

# Monorepo image
gh workflow run monorepo-docker.yml --ref <branch>

# Node services (single unified image)
gh workflow run node-services-docker.yml --ref <branch>

# Include arm64 (multi-arch, slower)
gh workflow run rust-docker.yml --ref <branch> -f include_arm64=true

--ref defaults to main if omitted.

After Triggering

  1. Get the run URL:

    gh run list --workflow=<workflow>.yml --limit=1 --json url --jq '.[].url'
    
  2. Get the run ID (wait a few seconds after triggering for the run to appear):

    gh run list --workflow=<workflow>.yml --limit=1 --json databaseId,status,createdAt --jq '.[0]'
    
  3. Watch it:

    gh run watch <run-id>
    
  4. The resulting image tag will be <7-char-sha>-<YYYYMMDD>-<HHMMSS>, e.g. c558a9f-20260304-105241.

  5. Images are at ghcr.io/hyperlane-xyz/<image-name>:<tag>.

Instructions

  1. Ask the user which image(s) they want to build (agent, monorepo, node services, or all).
  2. Ask which branch/ref (default: main).
  3. Ask if arm64 is needed (default: no).
  4. Trigger the workflow(s) with gh workflow run.
  5. Fetch and report the run URL(s) using gh run list.
  6. Optionally watch for completion if the user wants to wait.

References

  • To find existing images instead of building, use the /find-docker-image skill.
  • See docs/docker-image-policy.md for the full Docker image policy.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall