Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Runs the same rubric as the @claude CI reviewer, so you catch issues before a
maintainer does — but over your whole PR diff. (The CI scopes itself to
src/diffusers/, tests/, and .ai/; for your own PR, also review your docs
and scripts.) You're already on the branch with the conventions loaded, so: get
the
diff → review it against the rubric → report → iterate with the contributor
until it's ready, then remind them to share the final notes on the PR.
git diff main...HEAD # use your target branch if not main
If the branch trails main and the diff looks polluted with unrelated merged
files, scope to your own commits: git log main..HEAD --oneline, then
git show <commit>.
references/review-rules.md is the canonical rubric (the CI pins it from main) — read
it and review against it; don't rely on a remembered copy. For the areas you
touched, also read references/code_style.md, references/models.md, references/pipelines.md,
references/modular.md, references/testing.md, or references/pitfalls.md.
file.py:line →
impact. Cite the rule, e.g. Per references/models.md: "…only keep the inference path."path:line · Likely-dead / Used · reason.Report only — do not edit files. Be concrete, cite the rule, review the whole diff, and don't invent issues or flag pure style.
Expect several rounds: the contributor addresses findings, you review again. Keep working with them to fix as much as possible until the verdict is READY — the Leave for the actual review items are the only ones that should reach the reviewer unresolved. End the final round's report by reminding the contributor to share it on the PR (description or a comment) — it saves the reviewer a few rounds of back-and-forth. Never commit the notes as part of the diff.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when the user has written (or wants to write) a `ModularPipelineBlocks` subclass in a local Python file and needs to package it into a Hub-uploadable directory. Covers the workflow from a single `block.py` file to a published custom-block repo that consumers can load via `ModularPipeline.from_pretrained(<repo>, trust_remote_code=True)`.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。