agentleFS
badgidsbadgids/comfyui-development-skills/skills/comfyui-upstream-development/SKILL.md

comfyui-upstream-development

Skill4 starsChanged 44 days agoMITView on GitHub

Use when preparing changes intended for Comfy-Org repositories, aligning with current upstream architecture, reviewing RFC-related work, writing upstream-facing tests/docs, or preparing a PR-quality change for ComfyUI or related official repositories.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search open/current architecture and tests before designing a new abstraction.

    line 16
  2. Distinctive:

    Search RFCs for related proposals, but confirm shipped implementation separately.

    line 17
  3. Distinctive:

    Keep scope narrow enough to review.

    line 18
  4. Distinctive:

    Add or update tests that demonstrate the intended contract.

    line 19
  5. Distinctive:

    Update docs when public behavior changes.

    line 20
  6. Distinctive:

    Run the repository's current required checks.

    line 21
  7. Distinctive:

    Do not push, open a PR, or rewrite history unless explicitly requested.

    line 23
  8. Distinctive:

    Avoid solving a local extension problem by adding a core API unless the change is broadly justified.

    line 27
  9. Distinctive:

    When a change is substantial enough to intersect an RFC area, determine whether the current project expects an RFC before implementation.

    line 31
  10. Distinctive:

    Before calling an upstream change PR-ready:

    line 35
  11. Distinctive:

    verify current contribution guidance for the owning Comfy-Org repository.

    line 37
  12. Distinctive:

    keep the diff scoped to the intended contract.

    line 38
  13. Distinctive:

    add or update tests and public docs when required.

    line 39
  14. Distinctive:

    run the repository's relevant current checks.

    line 40
  15. Distinctive:

    do not push, rewrite history, or open a PR unless the user explicitly asks.

    line 42

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ComfyUI Upstream Development

Repository-local agent guidance

Before changing an official repository, inspect its current repository-local instructions when present: AGENTS.md, CLAUDE.md, .claude/skills/, .claude/commands/, .cursor/skills/, CONTRIBUTING files, and developer READMEs. Treat those as process guidance for that repository. Do not import the global comfy-claude-prompt-library wholesale, and do not let prompt guidance override the repository's implementation or version-matched API contract.

Procedure

  1. Refresh the relevant official repository and inspect current contribution guidance without modifying the user's checkout unexpectedly.
  2. Search open/current architecture and tests before designing a new abstraction.
  3. Search RFCs for related proposals, but confirm shipped implementation separately.
  4. Keep scope narrow enough to review.
  5. Add or update tests that demonstrate the intended contract.
  6. Update docs when public behavior changes.
  7. Run the repository's current required checks.
  8. Review the diff for accidental generated/vendor changes.
  9. Do not push, open a PR, or rewrite history unless explicitly requested.

Upstream compatibility

Avoid solving a local extension problem by adding a core API unless the change is broadly justified. Conversely, do not build fragile monkey patches when an upstream extension point already exists.

RFC use

When a change is substantial enough to intersect an RFC area, determine whether the current project expects an RFC before implementation. Do not invent process requirements; inspect current repository guidance.

Acceptance gate

Before calling an upstream change PR-ready:

  • verify current contribution guidance for the owning Comfy-Org repository;
  • keep the diff scoped to the intended contract;
  • add or update tests and public docs when required;
  • run the repository's relevant current checks;
  • inspect the final diff for accidental generated or vendor changes;
  • do not push, rewrite history, or open a PR unless the user explicitly asks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.