docs: adopt shared Omarchy badge in README and scaffolds - #20
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.
Makes the shared community badge easy to adopt: the bundle README now uses the pinned asset from tcballard/omarchy-badges, and newly generated plugin READMEs include the same one-line badge. Clicking the badge opens its reuse instructions.
The image URL pins the exact approved SVG commit, so future badge redesigns cannot change existing READMEs. The OpenAI adapter template is synced with the canonical scaffold. Existing generated projects are not rewritten.
Validation: all 55 tests and repository checks pass via ./scripts/test, skill validation passes, git diff --check passes, and the public raw SVG matches the approved local asset byte-for-byte. This does not publish a new bundle release.