Edit Operation Presets

Edit models are a different beast from generation models. You're not describing a scene from nothing - you're giving a change order: take what's there and alter it. And change orders have a grammar. This node is the pack's curated collection of that grammar: preset edit operations - the verb of the edit, what gets done - ready to drop into an image-edit workflow.

The dropdown's default is BLACK_BAR_CENSOR, and that tells you the neighborhood: this list is mostly style-and-content operations you'd apply to an existing image. There are censor/de-censor operations (black bar, mosaic), dress and undress presets, body-modification presets (make younger/older, increase/decrease detail, anatomy fixes, muscle changes), and composition edits. It's blunt about what it covers - this is the kind of preset family that exists because someone kept typing the same edit instructions over and over and finally made a dropdown. Pair it with its sibling UC_EditTargetPresets, which describes the what (the subject or region) while this one describes the how (the operation), and you have a two-part edit instruction that reads like a sentence.

Output is a single edit_op_prompt string, plus the usual escape_parentheses boolean ("prevents errors from parentheses left in the prompt") - keep that on for any text encoder that parses parentheses, because these are long instruction blocks. The string is meant to be concatenated with your target description and your own instructions before hitting the edit model's encoder.

Why this matters in 2026: modern edit models (the Qwen-image-edit family, Krea's edit model, and the VLM-driven edit chains this pack supports) read instructions like a chat message, not a tag list. The KB's prompt-engineering essay makes the case that these are instructions, and well-structured instructions are what LLM-based edit encoders reward. A preset operation block is precisely that - a fixed, tested instruction you don't have to re-derive. The reproducibility angle is the same as the rest of the pack's preset family: hold the operation constant while you vary the target and your scene-specific instruction, and the edit-variable isolation actually shows you what each part contributes.

The honest caveats: a preset is a strong opinion, and some of these operations (body-modification ones especially) are presets of a taste - flip through them and check they say what you actually want before trusting the label. And "operation" isn't "guarantee": an edit model may decline or fail an instruction it judges out of scope, so treat the output as the phrasing, not the outcome. Also note the preset is an instruction for editing, not a generation style - don't bolt it onto a plain text-to-image prompt and expect magic.

Install is pack-standard: Manager search "ComfyUI-UtilsCollection" or git clone into custom_nodes. No models, no downloads. If you've already got the pack for its edit-target presets or encoder nodes, this is one dropdown away.