Skip to content

aboylabs/ai-agent-skills / skills/creative/comfyui

comfyui

Flagged

Generate images, video, and audio with ComfyUI — install, launch, manage nodes/models, run workflows with parameter injection. Uses the official comfy-cli for lifecycle and direct REST/WebSocket API for execution.

FileKindSize
SKILL.mdskill md23.5 KB
references/official-cli.mdmarkdown7.4 KB
references/rest-api.mdmarkdown10.1 KB
references/workflow-format.mdmarkdown7.8 KB
scripts/_common.pyscript33.0 KB
scripts/auto_fix_deps.pyexecutablescript8.1 KB
scripts/check_deps.pyexecutablescript16.8 KB
scripts/comfyui_setup.shexecutablescript10.2 KB
scripts/extract_schema.pyexecutablescript11.0 KB
scripts/fetch_logs.pyexecutablescript5.6 KB
scripts/hardware_check.pyexecutablescript17.4 KB
scripts/health_check.pyexecutablescript8.0 KB
scripts/run_batch.pyexecutablescript8.9 KB
scripts/run_workflow.pyexecutablescript30.9 KB
scripts/ws_monitor.pyexecutablescript10.3 KB
tests/README.mdmarkdown2.1 KB
tests/conftest.pyscript1.4 KB
tests/pytest.iniconfig132 B
tests/test_check_deps.pyscript2.3 KB
tests/test_cloud_integration.pyscript4.2 KB
tests/test_common.pyscript16.0 KB
tests/test_extract_schema.pyscript7.8 KB
tests/test_run_workflow.pyscript8.5 KB
workflows/README.mdmarkdown3.8 KB
workflows/animatediff_video.jsonconfig2.0 KB
workflows/flux_dev_txt2img.jsonconfig2.2 KB
workflows/sd15_txt2img.jsonconfig1.4 KB
workflows/sdxl_img2img.jsonconfig1.6 KB
workflows/sdxl_inpaint.jsonconfig1.8 KB
workflows/sdxl_txt2img.jsonconfig1.4 KB
workflows/upscale_4x.jsonconfig864 B
workflows/wan_video_t2v.jsonconfig2.1 KB

tests/README.md

View on GitHub
# ComfyUI Skill Tests

Pytest suite covering the skill's scripts. Pure-stdlib unit tests run
without any setup; cloud integration tests need a Comfy Cloud API key.

## Running

```bash
# Unit tests only (no network required) — runs in <1s
python3 -m pytest tests/ -c tests/pytest.ini -o addopts="-p no:xdist"

# Including cloud integration tests
COMFY_CLOUD_API_KEY="comfyui-..." python3 -m pytest tests/ \
  -c tests/pytest.ini -o addopts="-p no:xdist"

# Just cloud tests
COMFY_CLOUD_API_KEY="comfyui-..." python3 -m pytest tests/test_cloud_integration.py \
  -c tests/pytest.ini -o addopts="-p no:xdist" -v
```

The `-c` and `-o` overrides isolate this suite from any parent
`pyproject.toml` pytest config (e.g. the `-n auto` from a parent repo).

## Test files

| File | Coverage |
|------|----------|
| `test_common.py` | Cloud detection, URL routing, format validation, embeddings, paths, seeds, model-list parsing, folder aliases |
| `test_extract_schema.py` | Connection tracing, positive/negative prompt detection, dedup logic, embedding deps |
| `test_run_workflow.py` | Param injection (incl. -1 seed, link refusal), output download walk, runner construction |
| `test_check_deps.py` | Model-name fuzzy matching, install command suggestions |
| `test_cloud_integration.py` | Live cloud API contract tests (auto-skipped without API key) |

## Adding tests

When you change a script:

1. Add a unit test if the change is pure logic (cloud detection, parsing, etc.)
2. Add a cloud integration test if the change depends on cloud API behavior
   (use `pytestmark = pytest.mark.cloud` so it auto-skips without a key)
3. Workflow fixtures live in `conftest.py` (`sd15_workflow`, `flux_workflow`,
   `video_workflow`)

## Why the explicit `-c` / `-o`?

The parent hermes-agent repo's `pyproject.toml` enables `pytest-xdist` by
default (`-n auto`). This suite is small enough that parallelism isn't
worth the complexity, and pytest-xdist isn't always installed in the user's
environment. The `-c tests/pytest.ini -o addopts="-p no:xdist"` flags make
the suite run identically regardless of the parent project's config.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall