What problem does it solve?
Publishing a ComfyUI custom node pack to the Comfy Registry involves strict rules around node class structure, pyproject.toml metadata, immutable versioning, and API-key-based publishing, and mistakes like a missing Repository URL or a wrong PublisherId cause publish failures.
Core Features & Use Cases
- Node Pack Authoring: Defines the required package structure, including init.py mappings, the node class contract (INPUT_TYPES, RETURN_TYPES, FUNCTION, CATEGORY), and input widget option schemas.
- Registry Metadata & Publishing: Specifies every pyproject.toml field rule (name, version, PublisherId, Icon, Banner) plus the comfy-cli publish flow and one-time registry setup.
- CI Automation: Provides a GitHub Actions workflow that publishes automatically when pyproject.toml changes on the main branch.
- Use Case: A developer finishes a custom node, runs comfy node init, fills in PublisherId and Repository, bumps the version, and publishes to registry.comfy.org via comfy node publish or a push-triggered GitHub Action.
Quick Start
Help me scaffold a ComfyUI custom node pack with the correct pyproject.toml and publish it to the Comfy Registry using comfy-cli.