repairing-workflows

Classifies ComfyUI execution errors and plans minimal partial reruns of failed workflow subgraphs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ShinyGua/ComfyUI-Agent --skill repairing-workflows-shinygua
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repairing-workflows
Source: https://github.com/ShinyGua/ComfyUI-Agent/tree/main/.claude/skills/repairing-workflows
Command: npx skills add https://github.com/ShinyGua/ComfyUI-Agent --skill repairing-workflows-shinygua

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a ComfyUI prompt fails validation or crashes mid-execution, re-running the entire workflow wastes time and compute. This Skill classifies the failure into a concrete error class and computes the smallest set of nodes that must be re-executed, so only the broken subgraph runs again. ## Core Features & Use Cases - Error classification: Reads node_errors from POST /prompt responses or execution_error WebSocket frames and assigns one of four classes: link, parameter, default, or missing_resource. - Deterministic repair recipes: Reference docs define JSON patch strategies per class, such as fixing link tuples, clamping parameter values to /object_info ranges, or substituting missing model filenames. - Partial rerun planning: Computes partial_execution_targets as the descendants of the failed node intersected with ancestors of the output nodes, letting ComfyUI reuse cached upstream results. - Use Case: A KSampler node fails with cfg must be <= 30. The classifier returns class parameter, the prompt is patched with a clamped value, and only the sampler, decoder, and save nodes are re-submitted instead of the full graph. ## Quick Start Ask the agent to diagnose the failed ComfyUI run, classify the error, patch the prompt, and re-run only the affected nodes.

Frequently Asked Questions about repairing-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a failed ComfyUI workflow without re-running everything?▼

Classify the error first, patch only the affected prompt JSON, then compute partial_execution_targets covering the failed node and its descendants up to the output nodes. ComfyUI reuses cached upstream outputs, so only the broken subgraph re-executes.

What types of ComfyUI errors can be classified automatically?▼

Four classes are supported: link errors like bad_linked_input, parameter errors like validation failures or out-of-range values, default errors from required_input_missing, and missing_resource errors when a checkpoint, LoRA, or VAE filename is not on disk.

How does partial execution work in ComfyUI?▼

Partial execution submits the prompt with a partial_execution_targets list containing only the failing node and its downstream descendants that lead to output nodes. ComfyUI skips re-computing upstream nodes whose results are already cached.

What does a value_not_in_list error mean in ComfyUI?▼

It means a filename field such as ckpt_name, lora_name, or vae_name references a file not present on disk. The repair is to list available models via folder_paths or /object_info and substitute the closest matching filename, or prompt the user through a setup wizard.

When should errors not be routed to the repair loop?▼

Evaluator failures where criteria are simply not met should go to the planner, not the repair loop. The repair loop only handles engine-level errors from node_errors validation responses or execution_error WebSocket frames.