docs: pair README badges with consistent GitHub topics - #22
Merged
Merged
Conversation
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.
Adds the agreed discovery convention to the scaffold skill and its generated README guidance:
Generated shell-plugin READMEs recommend omarchy and omarchy-plugin. Guidance explains that a README badge does not set GitHub metadata, preserves existing relevant topics, and applies metadata changes only when in scope. This remains a community convention rather than a marketplace requirement.
The canonical skill, its reference and README template are synced into the OpenAI adapter.
Validation: all 55 local tests and repository checks passed; skill validation and git diff --check pass. No repository topics were changed and no release was published.