Repository navigation
docs(docs): restyle the npm downloads badge like skills.sh and drop the version badge - #75
Merged
Merged
Conversation
…he version badge The downloads badge becomes all npm red with the white npm logo and reads "npm 816", like the skills.sh badge next to it (one color, a logo, a short label, a plain number). It stays a dynamic JSON badge on npm's last-week count, since shields' npm/dw badge always appends "/week". The npm version badge goes: the skill, plugin and MCP config all run `npx -y`, which always fetches the latest release, so the version doesn't change anything for users, and the downloads badge already links to the npm page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 2026
|
🎉 This PR is included in version 0.5.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Look at the badge row under the title.
Follows #74, which merged before these changes were pushed to it.
What
Why
#CB3837), a logo, a short label and a plain number. It's still a shields.io dynamic JSON badge onapi.npmjs.org/downloads/point/last-week/@makemyclip/editor, because shields' built-innpm/dwbadge always adds "/week". The logo is shields' built-innpmicon in white.npx -y @makemyclip/editor, which always fetches the latest release, so users never choose a version. The downloads badge links to the same npm page.Release
This doesn't release.
.releaserc.jsonuses the angular preset, wheredocscommits don't trigger a release, and its custom rules cover onlychore(deps)andchore(security). #74's merge didn't release either: npm is still at 0.5.1.Checks
npm: 816, matching the npm API's last-week count. Checked in renders against GitHub's light and dark backgrounds.pnpmchecks: Biome and the tests don't cover README.md.