# Reorganise Comfy Workflow

> Reorganise an existing ComfyUI workflow layout without changing runtime behavior. Use when the user asks to clean up a messy graph, make it readable, regroup or align nodes, or run the explicit `/reorganise_comfy_workflow` agent route.

- Skill: `peteromallet/reorganise-comfy-workflow` (Agent Skill)
- Install (CLI): `npx skillmds@latest add peteromallet/reorganise-comfy-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/peteromallet/reorganise-comfy-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: peteromallet (https://skillmd.com/u/peteromallet)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/peteromallet/reorganise-comfy-workflow

---


# Reorganise Comfy Workflow

Use this when the graph should become easier to review, share, or maintain, but the workflow semantics must stay unchanged. A JSON canvas is an input or presentation artifact; load the canonical Python bundle before judging semantic equivalence. This is a layout-only path: it may move, resize, group, color, flag, or annotate UI furniture, but it must not edit topology, node classes, links, widget values, prompts, runtime payloads, or generated graph state.

The explicit route is available now. Automatic main-flow integration is
conservative: the default mode can suggest this skill after a successful
functional edit, but it does not silently reorganise, auto-apply, or start a
second edit phase.

## CLI Path

Start with deterministic offline evidence:

```bash
vibecomfy reorganise workflow.json --assess
```

Create a preview candidate before any write to the source workflow:

```bash
vibecomfy reorganise workflow.json --preview --out cleaned.json
```

Preview writes sibling artifacts next to `cleaned.json`:

- `reorganisation_plan.json`
- `reorganisation_report.md`
- `reorganisation_metrics.json`
- `structural_noop_evidence.json`
- `reorganisation_preview_manifest.json`

Apply only an existing preview manifest:

```bash
vibecomfy reorganise workflow.json --apply --manifest reorganisation_preview_manifest.json --out cleaned.json
```

Replacing the source workflow is deliberately explicit:

```bash
vibecomfy reorganise workflow.json --apply --manifest reorganisation_preview_manifest.json --replace-original
```

In-place apply preserves a sibling `.bak`. Apply refuses stale source graphs by checking the preview manifest source hashes and writes the exact previewed candidate instead of recomputing a new layout.

Useful options:

```bash
vibecomfy reorganise workflow.json --preview --out cleaned.json --spacing compact
vibecomfy reorganise workflow.json --preview --out cleaned.json --existing-group-policy preserve
vibecomfy reorganise workflow.json --preview --out cleaned.json --force-regroup
vibecomfy reorganise workflow.json --preview --out cleaned.json --sidecar workflow.layout.json
```

## Agent Route

For Comfy app agent turns, use the explicit route:

```text
/reorganise_comfy_workflow
```

or send `route="reorganise"`.

The route runs after normal durable turn allocation. It should produce a reviewable layout candidate, report, metrics, structural no-op evidence, and candidate UI artifact when gates pass. It must use the existing candidate, idempotency, accept/reject, and apply-eligibility flow; do not introduce a parallel apply path.

Explicit organisational prompts such as "organise this workflow", "clean up the
canvas", and "make this readable" canonicalize to `route="reorganise"` with
`task="layout_reorganise"`. Unknown explicit routes still fail closed through
the normal clarify path.

## Main-Flow Suggestions

Post-edit reorganisation is controlled by:

```text
VIBECOMFY_REORGANISE_AUTO=off|suggest|candidate
```

- `off`: default. Do not inspect successful edits for a follow-up layout offer.
- `suggest`: After a successful applyable functional candidate, attach
  compact `layout_reorganisation` advisory metadata and mention
  `/reorganise_comfy_workflow` when deterministic before/after layout evidence
  shows the result may be harder to review. The functional candidate remains
  unchanged.
- `candidate`: experimental rollout mode. Only after a successful applyable
  functional candidate, prepare a layout-only reorganise candidate through the
  same durable candidate lifecycle. If preview, structural no-op, or apply
  eligibility checks fail, keep the functional candidate and fail closed.

Invalid config values fail closed to `off` with visible config metadata. In all
modes, functional user intent stays on the functional route; compact layout
hints must not override a concrete edit request.

## Review Discipline

- Treat the result as a candidate, not an applied edit.
- Confirm `layout_only_structural_noop` is true before presenting an apply path.
- Confirm the structural/topology hash is unchanged apart from UI-only layout
  fields. Reorganisation must never add, remove, rewire, or retarget runtime
  nodes, links, widgets, prompts, or generated API payloads.
- Use `reorganisation_report.md` for the user-facing summary and `structural_noop_evidence.json` for safety evidence.
- After a successful preview, tell the user where the organised `.json` and
  artifacts were written, and offer to open that output folder for review.
- Also offer a manifest-backed replace-original option. Make clear that replacing
  the original requires `--apply --manifest reorganisation_preview_manifest.json
  --replace-original`; this writes the exact previewed candidate and creates a
  sibling `.bak` backup of the original workflow. Do not describe replacement as
  happening by omission of `--out`.
- If parse, validation, compile, stale-source, invalid-ref, duplicate-ownership, or structural-drift checks fail, report that no candidate is available.
- Do not call semantic providers for CLI assessment or default preview. Provider-backed planning is an explicitly injected orchestration path, not the default skill behavior.
- If the user asks for functional graph changes after layout cleanup, hand off to `edit-comfy-workflow`.