Repository navigation
chore(skills): re-vendor the documents that moved upstream - #84
Merged
Merged
Conversation
Automated by the scheduled skill-drift job. Moved: devup-ui.
owjs3901
approved these changes
Oct 5, 2026
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
1 participant
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.
The embedded copies of these skills fell behind their source repositories: devup-ui.
Those copies are what
devup_skills installwrites on a machine with no network, so a stale one installs rules the upstream project no longer states.cargo testcannot see this: it checks the manifest against the documents in this tree, which agree with each other while both are behind.Produced by
node scripts/refresh-skills.mjsin the scheduledskill-driftjob. Review the diff as you would any skill change - it is upstream prose, not generated code.