Loading...
Loading...
Found 33 Skills
Automated release workflow for oh-my-claudecode
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 and merge it into main and develop with a tag.
Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version.
Generate release notes from commits since last tag
Ship a new dtctl release — bump version, write changelog entries, run tests, commit, tag, push, and write GitHub release notes. Use this skill whenever the user says "release", "ship it", "cut a release", "new version", "bump version", "publish", or asks about the dtctl release process. Also use when the user wants to update CHANGELOG.md for a release or write GitHub release notes.
Provides a step-by-step procedure for generating Gemini CLI changelog files based on github release information.
GitHub release workflow with semantic versioning, changelogs, and release automation using gh CLI. Use when creating releases, tagging versions, or publishing changelogs.
Universal release automation. CHANGELOG, commit, tag, GitHub Release supported. Use when user mentions release, version bump, create tag, publish release. Do NOT load for: harness release (use x-release-harness instead).
Create a git release — tag, push, and create GitHub release
First-time setup for the gman-skills package. Checks whether the dotnet-blazor plugin is installed and installs it when missing. Checks whether the report-server binary exists and downloads it from GitHub Releases when missing. Run once after `npx skills add gvdvenis/gman-skills`. Triggers on: "setup gman skills", "/setup-gman-skills", "install gman skills dependencies".
Create versioned releases with consolidated changelogs. Gathers shipped items, generates CHANGELOG.md entry, creates git tag, and GitHub Release. Use after multiple /ship tasks are merged.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.