Comfy Org
Official@comfy-org
Offers specialized engineering capabilities for managing ComfyUI node-based graph compositions, end-to-end testing, and narrative video production orchestration.
Agent Skills by Comfy Org
Showing 27 vetted skills indexed across 2 GitHub repositories.
Comfy-Orgcomfy-build
Builds reproducible ComfyUI environments into versioned releases on the Comfy developer platform.
Comfy-Orgcomfy-deploy-failures
Diagnose Comfy Cloud deployment failures by mapping deploy error codes to fixes.
Comfy-Orgcomfy-deploy
Deploy ComfyUI build releases as serverless endpoints using comfy-cli deploy commands.
Comfy-Orgcomfy-build-pins
Diagnose and resolve pip dependency conflicts in comfy-build.yaml pipDependencies before building.
Comfy-Orgremoving-typescript-suppressions
Replaces @ts-expect-error and @ts-ignore directives with minimal type-safe fixes.
Comfy-Orgconsolidating-test-setup
Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner.
Comfy-Orgdisabling-ai-attribution
Disables AI attribution in Claude Code, Amp, and Codex contributor settings.
Comfy-Orgregenerating-screenshots
Creates a labeled PR that triggers the GitHub Action to regenerate Playwright screenshot expectations.
Comfy-Orglayer-audit
Detects layered architecture import violations using ESLint no-restricted-paths rules.
Comfy-Orghardening-flaky-e2e-tests
Diagnoses and fixes flaky Playwright e2e tests by replacing race-prone patterns with retry-safe assertions.
Comfy-Orgadding-deprecation-warnings
Adds backward-compatible deprecation warnings for renamed or removed TypeScript properties.
Comfy-Orgcontain-audit
Detects DOM elements where CSS containment improves rendering performance via Playwright audits.
Comfy-Orgadd-model-page
Adds, updates, or removes model page entries on the Comfy Org website via pull requests.
Comfy-Orgwriting-storybook-stories
Write and update Storybook stories for Vue components in ComfyUI_frontend.
Comfy-Orgbackport-management
Manages cherry-pick backports of merged PRs to stable release branches on GitHub.
Comfy-Orgreviewing-unit-tests
Reviews Vitest unit-test diffs in ComfyUI_frontend against documented testing rules.
Comfy-Orgpublishing-a-new-package
Publishes monorepo packages to npm and verifies consumer installation end to end.
Comfy-Orgcodegen-transform
Converts raw Playwright codegen output into ComfyUI convention-compliant test code.
Comfy-Orgrecovering-poisoned-asset-cache
Diagnose and recover cached 404s on CDN-served frontend asset chunks.
Comfy-Orgperf-fix-with-proof
Ships performance fixes as stacked PRs with CI-proven improvement deltas.
Comfy-Orgred-green-fix
Fixes bugs as two commits so CI proves the regression test catches the bug.
Comfy-Orgcomfy-debug
Diagnose comfy-cli failures by mapping JSON envelope errors to recovery actions.
Comfy-Orgcomfy
Automate ComfyUI setup, workflow composition, and job execution from the command line.
Comfy-Orgcomfy-relay
Present generated images, videos, and audio previews in chat for review.
Frequently Asked Questions About Comfy Org
FAQPage SchemaWhat specific tasks can engineers perform using Comfy Org's capabilities?▼
Engineers can perform end-to-end testing of frontend interfaces, decompose large JSON graph structures into reusable fragments, and orchestrate complex multi-shot video production sequences. These capabilities enable systematic debugging of node-based execution environments and streamlined management of visual media generation pipelines.
Which technical personas benefit most from these capabilities?▼
These capabilities are designed for frontend engineers maintaining visual interfaces, technical directors managing generative media pipelines, and systems engineers responsible for node-based graph stability. The feature set specifically targets those managing complex JSON-based visual generation environments and requiring robust testing and modular composition.
What are the primary prerequisites for implementing these capabilities?▼
Implementation requires an existing ComfyUI environment and familiarity with JSON-based graph structures. Users must have the core runtime environment configured to support node-based execution, as these capabilities rely on mapping specific JSON envelope errors and managing graph-based dependencies for successful media generation and testing.