comfyui-core-runtime
Skill4 starsChanged 44 days agoMITView on GitHub
Use when changing or diagnosing ComfyUI core execution, server behavior, backend APIs, model loading, caching, scheduling, node execution internals, filesystem handling, or other code owned by the ComfyUI runtime rather than a third-party custom-node pack.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-custom-node-backendSkill
- comfyui-developmentSkill
- comfyui-frontend-extensionSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
If the comfyui-development router skill is installed, follow its shared authority/freshness policy.
- Distinctive: line 22
Search for the behavior and its tests rather than assuming old module paths.
- Distinctive: line 24
Check for feature flags, version guards, compatibility shims, or deprecations.
- Distinctive: line 26
Run the narrowest relevant tests, then broader tests if feasible.
- Distinctive: line 34
use an RFC as proof that code has shipped.
- Distinctive: line 36
update the user's checkout to upstream without permission.
- Distinctive: line 49
Before calling the change complete:
- Distinctive: line 54
verify public route, node, or workflow behavior when the change affects one.
- Distinctive: line 55
update public documentation when the supported contract changed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ComfyUI Core Runtime
If the comfyui-development router skill is installed, follow its shared authority/freshness policy. This specialist remains usable on its own.
Primary sources
- target/version-matched
Comfy-Org/ComfyUI; - matching/current
Comfy-Org/docs; - tests in the core repository;
- RFCs only for proposal/history context.
Procedure
- Establish the compatibility target and exact checkout/commit.
- Reproduce or locate the owning subsystem before editing.
- Search for the behavior and its tests rather than assuming old module paths.
- Trace call sites across the execution path.
- Check for feature flags, version guards, compatibility shims, or deprecations.
- Make the smallest behaviorally complete change.
- Run the narrowest relevant tests, then broader tests if feasible.
- For server/API changes, verify the actual route/payload behavior on a running target when practical.
- For node-facing changes, inspect resulting live node definitions or representative workflows.
Do not
- hardcode an internal path merely because it existed in a previous release;
- infer an API contract from an internal helper alone;
- use an RFC as proof that code has shipped;
- refactor unrelated code as part of a bug fix;
- update the user's checkout to upstream without permission.
Evidence for completion
At least one of these should exist before claiming the change works:
- relevant automated tests pass;
- a minimal runtime reproduction passes;
- a server/API probe confirms the behavior;
- a representative workflow exercises the changed path.
Acceptance gate
Before calling the change complete:
- record or identify the target ComfyUI commit/version;
- show that the change addresses the owning execution path;
- pass a focused test or minimal runtime reproduction;
- verify public route, node, or workflow behavior when the change affects one;
- update public documentation when the supported contract changed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

