diffusers-cli

Solid

Use when the user wants to run a diffusers pipeline from a terminal (one-off generation, batch jobs, smoke-testing a new model), run on HF Sandbox hardware via `--remote`, introspect a pipeline's input schema before calling it, or attach a LoRA at inference time. Prefer this over writing ad-hoc Python scripts for generation tasks.

AI & Automation 55 stars 2 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

## Overview `diffusers-cli` is the shipped CLI in `src/diffusers/commands/`. Subcommands relevant to agentic use: | Command | Purpose | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `run` | Run any `DiffusionPipeline` or `ModularPipeline`. Forwards `--pipeline-kwargs` verbatim, saves output by detecting its runtime type, optionally runs on HF Jobs via `--remote`. | | `schema` | Print the input schema for a pipeline repo (kwarg names, types, defaults, descriptions). **No weights downloaded** — only the small index file. | | `custom_blocks` | Package a local `ModularPipelineBlocks` subclass for the Hub. | | `env` | Print versions of diffusers + torch + transformers + accelerate + safetensors + CUDA + GPU info. Use when investigating environment issues, dtype/precision support, or building bug reports. | ## When to read which file Most agentic work goes through `run`. Read the matching reference file before constructin...

Details

Author: modem-dev
Repository: modem-dev/ossrules
Created: 1 weeks ago
Last Updated: 5 days ago
Language: Python
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

model-integration

Use when adding a new model or pipeline to diffusers, setting up file structure for a new model, converting a pipeline to modular format, or converting weights for a new version of an already-supported model.

55 Updated 5 days ago

modem-dev

Data & Documents Solid

pipeline-digest

Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, which branches went stale, and GitHub issue/PR activity, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship", "pipeline digest", "any repo activity", or when the `pipeline-digest` routine fires. For a full on-demand pipeline snapshot regardless of change, use /release-status instead.

74 Updated today

gtapps

Code & Development Listed

pocket-diff

Publishes the current git diff as a self-contained Artifact page that reads like an IDE diff on a phone. Built for Remote Control sessions, where the phone shows only the chat: use it whenever the user wants to see or review changes away from their desk — 'show me the diff', 'send me the diff', 'let me read this on my phone', 'review the changes on mobile' — or when /pocket-diff is invoked. Prefer it over printing a diff into the conversation: a script builds the page, so the diff never reaches the model's context.

1 Updated 5 days ago

tahaakocer