Release
Bump version, commit, push, and create a GitHub release with changelogFrom its SKILL.md
npx -y skills add laat/mor --skill releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Create a release for mor. The user provides the version number (e.g. /release v0.12.0).
Steps
-
Parse version: Strip leading
vif present to get the semver (e.g.0.12.0). The tag usesvprefix (e.g.v0.12.0). -
Pre-flight check: Run
pnpm prepublishOnly(lint, test, build) before making any changes. If it fails, stop and fix the issues first. -
Find previous release tag: Run
gh release list --limit 1to get the latest release tag. -
Build changelog: Run
git log <previous-tag>..HEAD --onelineto get all commits since the last release. Group them into sections:- Features — new functionality
- Fixes — bug fixes
- Docs — documentation changes
- Internal — refactoring, tests, build changes
Skip version bump commits. Write concise user-facing descriptions, not raw commit messages.
-
Show the changelog to the user and ask for approval before proceeding.
-
Bump version: Update
versioninpackage.json,.claude-plugin/plugin.json, and the.THheader line ofman/mor.1to the new semver. The.THline inman/mor.1also carries a release date — update it to today's date inYYYY-MM-DDformat. Format:.TH MOR 1 "<date>" "mor <semver>" "User Commands". -
Commit and push: Commit with message
<semver>(e.g.0.12.0), then push. -
Create GitHub release: Run
gh release create v<semver>with the changelog as the body. Use## What's newas the top-level heading. -
Publish to npm: Publishing happens automatically via the
publish.ymlGitHub Actions workflow, triggered by thev*tag created in step 8. No manual publish step is needed.