Results for “release-manager”

Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.

Use when the user asks to release, version, tag, or publish.

Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.

Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Automates the full release workflow for a single-package GitHub repository, from analysis through changelog authoring and PR creation using gh and git.

Fencang Release

Begins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either an explicit version or a natural-language description of the release.

Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up.

Version bump, generate changelog, tag, and prepare a release

Generates the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

Transform technical tickets, PRDs, or changelogs into polished, user-facing release notes organized by category.

Changelog Generator

Changelog Generator

口令「分仓」触发：将 DEV-workspace 中 app/code/Weline 模块同步到项目兄弟目录“框架-分仓” 下的独立 Composer 分仓；本地缺仓库时自动从 Gitee/GitHub clone，递增 git tag 后推送并刷新 Packagist。 仅在用户明确说出口令「分仓」时加载；不得因闲聊、发布、部署等相近词自动触发。 Keywords: 分仓, fencang, split-repo, composer sync, weline mirror.

Write release notes, changelogs, migration guides, deprecation notices, and version announcements that communicate changes clearly to users and developers. Use when shipping a new version, deprecating features, or guiding users through breaking changes. Also trigger for 'release notes', 'changelog', 'migration guide', 'breaking changes', 'deprecation notice', 'version update', 'what's new', or 'upgrade guide'.

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

Draft release notes from a list of merged changes.

Manages semantic versioning and changelog documentation for Flutter projects, defining a structured process for recording additions, changes, and removals across backend and mobile releases.

Generate consistent, auditable release notes from Conventional Commits, compute semantic version bumps, and enforce commit format linting.

CI release engineer skill for validation gating, release-readiness checks, and automation-safe delivery criteria.

Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).

Finalizes a release and merges it into main and develop with a tag using git-flow, then prunes stale branches and worktrees. This skill should be used when the user asks to "finish a release", "merge release branch", "complete release", "git flow release finish", or wants to finalize a release.

Manage tool versions and tasks with mise (formerly rtx). Use when a user asks to manage Node.js/Python/Go versions per project, replace nvm/pyenv/asdf, or define project-level tool requirements.

Internal technical readiness drill assistant for release and handoff.

Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.