mirror of
https://github.com/Comfy-Org/comfy-skills.git
synced 2026-11-04 23:37:45 +00:00
[PR #21] [MERGED] feat(comfy-build): scaffold the builder skill under comfy-cli/ #20
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/comfy-skills#20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Comfy-Org/comfy-skills/pull/21
Author: @james00012
Created: 8/20/2026
Status: ✅ Merged
Merged: 8/21/2026
Merged by: @james00012
Base:
main← Head:feat/comfy-build-skill-scaffold📝 Commits (2)
e76914cfeat(comfy-build): scaffold the builder skill under comfy-cli/c924d6bci: pin the validate workflow's actions and drop credential persistence📊 Changes
3 files changed (+93 additions, -0 deletions)
View changed files
➕
.github/workflows/validate-skills.yml(+45 -0)📝
README.md(+1 -0)➕
comfy-cli/comfy-build/SKILL.md(+47 -0)📄 Description
Why
comfy skills installis about to fetch a sixth skill from this repo, so that revising the builder skill's judgment never waits on a comfy-cli release. This PR is the container that fetch resolves to: valid to the installer's contract, and empty of the judgment the build features fill in.Change: [comfy-skills] The builder skill's scaffold and home · Feature: the builder skill reaches the user's agent · Design: Local agent access to the builder via comfy-cli skills
What lands
comfy-cli/comfy-build/SKILL.md: one directory, one file,name:frontmatter equal to the directory name. A signpost body saying what will fill it and telling an agent not to improvise a build in the meantime, since cutting a version costs the user money.comfy-cli/folder: skills that comfy-cli's installer fetches, as a sibling ofopenclaw/, which already groups a directory-shaped skill by the host that consumes it..github/workflows/validate-skills.yml: runs the CLI's owncomfy skills validateover every directory undercomfy-cli/. The contract lives in the CLI, not restated here.comfy-cli/, since the layout list is the only place that says where a file belongs.Where this sits
Validation
Local stack, end to end: comfy-cli 1.16-equivalent from source (
comfy_cliat0a6cb6e), against this working tree:comfy skills validate comfy-cli/comfy-build→{"valid": true, "name": "comfy-build", "bundled": false}.comfy skills install --scope project --skill <abs path>/comfy-cli/comfy-build→wrotefor all three targets:.claude/skills/comfy-build/SKILL.md,.cursor/rules/comfy-build.mdc, and a<!-- comfy-build:start -->fence inAGENTS.md.Not run: the new CI workflow itself, which first executes on this PR, and anything involving a remote fetch, which is the comfy-cli change's job.
Departures from the plan
Three, all declared
skills/tocomfy-cli/. The plan saidskills/comfy-build/SKILL.mdand called it "first of its kind in the repo". Both are wrong against the repo as it stands: this README documentsskills/as legacy and frozen pending removal with thecomfy-cloud-mcpcurl installer, andopenclaw/comfy/SKILL.mdis already a directory-shaped skill carryingname:/description:frontmatter that passes the CLI's contract today.maininstead, so no tag is cut here and the CLI resolvesmainon every install.name:, otherwise fails on a user's machine at install time rather than on the PR that broke it.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.