Repository navigation
Add check that federated skill names never change - #6
Merged
Merged
Conversation
lemonade-router-builder, local-ai-app-integration, and local-ai-use are federated to github.com/amd/skills, so their folder names and SKILL.md frontmatter names must stay fixed. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
Adds a
Skill Namesworkflow that fails if any of the three federated skills is renamed. These skills are sent to amd/skills, so their names must stay fixed:lemonade-router-builderlocal-ai-app-integrationlocal-ai-useA skill's name lives in two places, and the check covers both:
skills/<name>/SKILL.mdmust exist. This catches a renamed or deleted folder.name:field inSKILL.mdmust match exactly.It runs on every pull request, on pushes to
main, and on manual dispatch. There is no path filter, so it can be made a required check without getting stuck as pending on PRs that don't touch skills.Test plan
Ran the check script locally:
local-ai-usefrontmatter tolocal-ai-usagefailslocal-ai-usefolder fails