hummingbot-developer

Coordinates builds of hummingbot, gateway, and hummingbot-api repositories into a unified development workflow.

31|8|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/hummingbot/skills --skill hummingbot-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hummingbot-developer
Source: https://github.com/hummingbot/skills/tree/main/skills/hummingbot-developer
Command: npx skills add https://github.com/hummingbot/skills --skill hummingbot-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires conda, node, pnpm, docker, git, curl, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers build, run, and test Hummingbot components directly from source by coordinating hummingbot, gateway, and hummingbot-api repos into a cohesive development workflow.

Core Features & Use Cases

  • End-to-end development workflow: build wheels, assemble Docker images, and run a local dev stack for rapid iteration.
  • Branch synchronization and local wiring: checkout multiple repos to aligned branches and wire local hummingbot into the API for immediate testing.
  • Comprehensive tests and verification: run smoke tests against API, Gateway, and connectors to ensure integrated operation.

Quick Start

Install dependencies, clone the three repositories, checkout the desired branches, build the Hummingbot wheel, and start the full development stack to test local changes.

Frequently Asked Questions about hummingbot-developer

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

FAQPage Schema
How do I build Hummingbot from source and test local changes across repositories?

To build Hummingbot from source, this workflow coordinates cloning the core, gateway, and API repositories, builds Python wheels, sets up the conda environment, and runs a local dev stack for testing.

What dependencies do I need to run a local Hummingbot development workflow?

Running a local Hummingbot development workflow requires conda, node, pnpm, docker, git, curl, and python3 installed to manage environments, build wheels, assemble Docker images, and wire local repositories.

How does branch synchronization work when testing Hummingbot Gateway and API together?

Branch synchronization aligns the hummingbot, gateway, and hummingbot-api repositories to matching branches, ensuring integrated operation and consistent API-Gateway connectivity during local testing.

Can I use Docker to assemble and verify Hummingbot images during development?

Yes, Docker is used to assemble and tag Hummingbot images during the development workflow, verifying that local builds function correctly across the coordinated repositories before deployment.

What is the best way to wire local Hummingbot into the API for immediate testing?

The best way to wire local Hummingbot into the API is through an optional editable install, connecting your local build directly to the hummingbot-api repository for rapid iteration and smoke testing.

Why do my Hummingbot integration tests fail after building from source?

Integration tests may fail if repositories are on mismatched branches or if API-Gateway connectivity checks fail, making branch synchronization and wheel existence verification essential before running smoke tests.