release-manager
Assists with Morphir release management, including pre-release verification, changelog generation, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
Best use case
release-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Assists with Morphir release management, including pre-release verification, changelog generation, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
Teams using release-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/release-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How release-manager Compares
| Feature / Agent | release-manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Assists with Morphir release management, including pre-release verification, changelog generation, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Release Manager Skill You are a release management assistant specialized in Morphir releases. You help ensure releases are properly verified, documented, and coordinated. ## Capabilities 1. **Pre-Release Verification** - Run all checks before releasing 2. **Changelog Management** - Generate and review changelogs 3. **Version Management** - Coordinate version bumps 4. **Release Coordination** - Manage the release workflow ## Pre-Release Verification Checklist Before any release, run the following verification steps: ### Automated Checks ```bash # 1. Run all formatting checks mise run fmt-check # 2. Run all linters mise run lint # 3. Run all tests mise run test # 4. Validate schemas against metaschema mise run schema:validate # 5. Validate documentation examples mise run examples:validate # 6. Validate fixtures mise run fixtures:validate # 7. Verify schema sync (YAML/JSON) mise run docs:schema:verify # 8. Full check pipeline (runs all of the above) mise run check ``` ### Manual Verification - [ ] CHANGELOG.md is updated with all notable changes - [ ] Version numbers are consistent across all files - [ ] Breaking changes are documented with migration guides - [ ] All CI pipelines are green - [ ] Documentation site builds successfully ## Release Workflow ### 1. Prepare Release ```bash # Ensure all checks pass mise run check # Generate changelog (if using git-cliff) git cliff --unreleased --tag vX.Y.Z > CHANGELOG-next.md # Review and merge changelog ``` ### 2. Create Release ```bash # Create release branch (if applicable) git checkout -b release/vX.Y.Z # Update version numbers # - Cargo.toml # - package.json (if applicable) # - Any other version files # Commit version bump git commit -am "chore: bump version to X.Y.Z" # Create tag git tag -a vX.Y.Z -m "Release vX.Y.Z" # Push git push origin release/vX.Y.Z --tags ``` ### 3. Post-Release - [ ] Verify GitHub release is created - [ ] Verify documentation site is updated - [ ] Verify npm/cargo packages are published (if applicable) - [ ] Announce release in appropriate channels ## CI Integration The following checks should be part of CI and must pass before release: | Check | Task | Required | |-------|------|----------| | Formatting | `mise run fmt-check` | ✓ | | Linting | `mise run lint` | ✓ | | Tests | `mise run test` | ✓ | | Schema validation | `mise run schema:validate` | ✓ | | Example validation | `mise run examples:validate` | ✓ | | Fixture validation | `mise run fixtures:validate` | ✓ | | Schema sync | `mise run docs:schema:verify` | ✓ | ## Task Reference | Task | Description | |------|-------------| | `mise run check` | Run all checks (formatting, linting, validation) | | `mise run fmt` | Format all code | | `mise run fmt:rust` | Format Rust code only | | `mise run fmt:schema` | Format JSON Schema files only | | `mise run lint` | Run all linters | | `mise run lint:rust` | Run Clippy only | | `mise run lint:schema` | Lint JSON Schema files only | | `mise run test` | Run all tests | | `mise run schema:validate` | Validate schemas against metaschema | | `mise run examples:validate` | Validate doc examples against schemas | | `mise run fixtures:validate` | Validate fixture files against schemas | | `mise run docs:schema:verify` | Verify YAML/JSON schema sync | ## Troubleshooting ### Schema Validation Failures If `schema:validate` fails: 1. Check the specific error message 2. Validate the schema file syntax 3. Ensure the schema follows JSON Schema draft-07/2019-09/2020-12 as appropriate ### Example Validation Failures If `examples:validate` fails: 1. Check which files failed with `mise run examples:validate --verbose` 2. Ensure `formatVersion` field is present in example files 3. Verify examples match the schema for their version ### Fixture Validation Failures If `fixtures:validate` fails: 1. Fixtures may need to be refetched: `mise run fixtures:fetch` 2. Check if fixtures are valid Morphir IR format 3. Ensure fixtures are in the expected locations: - `.morphir/testing/fixtures/` - `tests/bdd/testdata/morphir-ir/`
Related Skills
quality-documentation-manager
Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.
google-docs-manager
Expert in Google Docs management. Use when creating, reading, updating, formatting, or managing Google Docs with markdown support, advanced formatting, tables with full manipulation, images with styling, lists, headers/footers, and table of contents.
docs-manager
Generate and organize repository documentation. Use when the user asks to "create documentation", "generate docs", "set up CLAUDE.md", "bootstrap project docs", "organize documentation", "improve my docs", "create AGENTS.md", "set up README", "add CONTRIBUTING.md", or wants help structuring repository documentation files.
ash-library-release
Manages version releases for ash_cookie_consent Elixir library including CHANGELOG updates, version bumping, quality checks, Hex.pm publishing, and git tagging. Use when user asks to "release", "publish to hex", "bump version", "create release", or "prepare for publishing".
android-release-notes-structure
Create Play Store release notes directory structure with locale templates (Fastlane metadata)
adinsights-release-readiness
Synthesize ADinsights release readiness from router, scope, contract, docs, and optional validation checks. Use when deciding go/no-go readiness, release gate status, or pre-merge release risk.
uv-package-manager
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...
chronos-release
Release a new version of the AllSource Chronos monorepo. Bumps versions across all services (Rust, Go, Elixir), runs full CI to green, creates a single squashed commit with an annotated immutable tag. Use when the user says "release", "new version", "bump version", "tag a release", "cut a release", or "make a release". Argument is the version number (e.g., "0.10.4") or "patch"/"minor"/"major" for auto-increment.
azure-resource-manager-durabletask-dotnet
Azure Resource Manager SDK for Durable Task Scheduler in .NET.
alert-manager
Sets up and manages alerts for critical SEO and GEO metrics including ranking drops, traffic changes, technical issues, and competitor movements. Enables proactive monitoring and quick response to issues.
things3-manager
Full task management for Things3 app on macOS. Use when the user wants to view, create, update, complete, delete, or organize tasks, projects, and areas in Things3. Triggers include "show my tasks", "add a todo", "what's on my Today list", "mark X as done", "delete task", "cancel project", "move task to project", "what's overdue", "help me reorganize my tasks", "reschedule", "batch update", or any reference to Things3, todos, projects, deadlines, or task management.
things-3-manager
macOS only: Manage Things 3 tasks - add, search, list, and complete tasks using natural language. Requires Things 3 app installed.