القائمة
Bump version, commit, push, and create a GitHub release with changelog
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The user's personal note store, accessed via the `mor` CLI. Check here first when the user asks to recall, find, or reuse something they previously saved.
Apply batch edits to notes using natural language — rename, retag, add cross-references, merge, or clean up a set of notes
Review the note store for quality issues — duplicates, stale content, broken links, tag inconsistencies, and cleanup opportunities
Reconcile docs (README, CLAUDE.md, man page, website) with the current source. Only fixes factual drift — does not rewrite prose.
Save a code snippet or piece of knowledge to the note store. Use when the user asks to remember, save, or store something for later.
| name | release |
| description | Bump version, commit, push, and create a GitHub release with changelog |
| disable-model-invocation | true |
Create a release for mor. The user provides the version number (e.g. /release v0.12.0).
Parse version: Strip leading v if present to get the semver (e.g. 0.12.0). The tag uses v prefix (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 1 to get the latest release tag.
Build changelog: Run git log <previous-tag>..HEAD --oneline to get all commits since the last release. Group them into sections:
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 version in package.json, .claude-plugin/plugin.json, and the .TH header line of man/mor.1 to the new semver. The .TH line in man/mor.1 also carries a release date — update it to today's date in YYYY-MM-DD format. 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 new as the top-level heading.
Publish to npm: Publishing happens automatically via the publish.yml GitHub Actions workflow, triggered by the v* tag created in step 8. No manual publish step is needed.
