Shima Conditioning Pass

Shima Conditioning Pass is a pass-through node with a job description that fits on a Post-it: conditioning goes in, the same conditioning comes out, nothing else happens. Its entire reason for existing is to make big graphs legible and to give Shima's Use Everywhere broadcast system a stable, type-safe place to land. If you've read the CLIP Pass article, you already know this family - this is the CONDITIONING-flavored twin.

What it's for

In a Shima workflow, the "islands" auto-connect via Use Everywhere: nodes broadcast their outputs and matching inputs anywhere on the canvas pick them up. The problem is that ComfyUI's auto-wiring likes to jam mismatched types into required inputs. Passers dodge that by declaring their input optional, so they become dependable landing pads - the docs call them "stable airports at the edge of each Island." A Conditioning Pass sitting between your Master Prompt and your sampler gives the broadcast a guaranteed, correctly-typed slot to dock into, instead of leaving the connection to chance.

The second use is pure organization. Conditioning wires are usually fat, long, and every-which-way across a busy graph. Running yours through a labeled Passer is the typed equivalent of a reroute - you get a clean break point that's easy to find and easy to follow.

The inputs and outputs

• conditioning (optional input) - a CONDITIONING object, e.g. the positive or negative output of a CLIP Text Encode or Shima's Master Prompt.
• conditioning (output) - the exact same object.

The source is one line: execute(self, conditioning=None): return (conditioning,). Optional in, identical out, zero processing.

When you'd use it

• As the receiving end of a Use Everywhere broadcast for conditioning.
• To run a single conditioning stream down a clean, labeled path instead of across the canvas.
• To leave a placeholder slot in a sub-workflow that sometimes gets conditioning and sometimes doesn't - the optional input handles both without erroring.

What it's not for: routing multiple conditionings, blending them, or choosing between them. This is single-signal plumbing. If you need to pick between two conditioning streams, that's a switch node's job; if you need both positive and negative on one wire, Shima's Pos/Neg Pass is the sibling that carries two.

Installing it

Part of the Shima pack - ComfyUI Manager → search Shima, or:

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf.git Shima

Restart ComfyUI. First launch auto-installs the pack's Python deps and companion repos (ComfyUI-Impact-Pack, cg-use-everywhere). Nothing to download for this node.

Common issues

The recurring trap is expectation: people wire this in and then wonder whether their prompt somehow got stronger or weaker. It didn't. The node is a wire with a name. If you're debugging and a conditioning signal "disappears" through a Passer, the Passer isn't the culprit - check what's feeding it.

One genuine pitfall to respect: because the input is optional, ComfyUI won't yell at you for leaving it empty, and an empty conditioning can flow onward and fail confusingly at the sampler. If you rely on a Passer as a placeholder, make sure you actually connect it before you queue - the pass-through only passes through what's there.