Repository navigation
feat(skills): add update-package-skill for release updates - #223
Merged
Merged
Conversation
A Skillgen update re-ran the whole authoring workflow. On which-nuxt 0.4.1, with a baseline tested against that same version, GLM 5.3 spent 61 of 71 steps re-testing every claim and debugging its own fixture server, and the run hit its 45 minute limit before review. update-package-skill diffs the tested version against the new one, re-tests only the Skill lines the diff touches, and leaves the copy byte-identical when nothing relevant changed, so Skillgen opens no pull request. The Harness runs it when the destination already holds the Skill; generate-package-skill stays the authoring path for a bootstrap.
1 of 6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Related to skilld-dev/skilld.dev#550
❓ Type of change
📚 Description
A Skillgen update ran the whole authoring workflow again. On which-nuxt 0.4.1, with a baseline already tested against that version, GLM 5.3 spent 61 of its 71 steps re-testing every claim and debugging its own fixture server. The run hit its 45 minute limit before review.
update-package-skilldiffs the version the Skill names against the new one, re-tests only the lines the diff touches, and keeps untouched lines byte-identical. When nothing relevant changed, it leaves the Skill as it was, so Skillgen opens no pull request. The Harness runs it for aPackageSkillwhose destination already holds the Skill.generate-package-skillstays the authoring path, and both Harness requests now say not to runskilldin the sandbox and to stop only the processes the Agent started.The skilld.dev runner can use it once a
skilld-harnessrelease includes it.