Review a diffusers contribution before opening a pull request. Check the full change against project rules, trace potentially unused code, and receive a severity-based report separating required fixes from points to discuss with reviewers.
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.
Review the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Package an existing custom diffusers block into a directory ready for Hub upload. Select a class from a Python file and save its source, configuration, and associated files so others can load the block.
Run diffusers generation pipelines from a terminal and save their outputs. Inspect accepted inputs without downloading model weights, apply LoRA adapters during generation, run remotely through HF Jobs, and inspect software and GPU environment details.
Integrate a model or pipeline into diffusers, from file structure and weight conversion to tests and documentation. Verify numerical agreement with the original implementation, with modular pipelines as the preferred starting point for new integrations.