Results for “release-pack”

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

Package skills into publishable plugin or bundle formats for ClawHub, Claude marketplace, and related runtimes. Use when: converting a skill into a plugin or release bundle, generating manifests, and assembling a release-ready upload directory. Not for standalone metadata optimization or deep security auditing.

Turn raw MATLAB code into a published .mltbx toolbox — full pipeline from scope definition through packaging and release. Drives 8 phases with human checkpoints, enforcing ordering and dependencies. Use when asked to package, create a toolbox, or run the files-to-package pipeline.

Traces software supply chain provenance from source to runtime, identifying divergence points in dependency resolution, build, packaging, and release pipelines.

Install, update, and manage the Hermes One desktop app via the `hermesone` npm package. Detects OS/arch, downloads verified releases, and installs with sha512 checksum verification.

Package skills into publishable plugin or bundle formats across ClawHub, Claude, Hermes, AgentSkill, AgentSkills.so, and GitHub. Use when: converting a skill into a release plugin, generating manifests, trimming runtime-only files, and assembling a breakout-ready upload artifact.

Fork, sanitize, and package private projects for safe public release through a three-stage pipeline.

Release Manager

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'.

Agent skill for release-swarm - invoke with $agent-release-swarm

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.

Builds a compact secret-safe repository pack for AI handoff, review, or large analysis; prefers Repomix when available.

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

Automates project releases with version bumping, multi-language changelog generation, and GitHub Release creation. Supports Node.js, Python, Rust, and generic projects.

Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.

Routes legacy release-manager references to the current runtime capability, preferring matching agents or modern plugin skills.

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.

Fencang Release

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

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.

Cut releases, validate changelogs, and manage git hooks for a project.

Composite skill — promote the long-lived `release` branch to `main`, cut a single version that batches every PR accumulated since the last tag, then clean up. Chains pr-merge-readiness (on release→main PR) → version-bump (semver from commits) → changelog-update (promote [Unreleased] → versioned) → ship (tag + GitHub release) → stale-branch cleanup → optional ship-it for deploy. Use this INSTEAD of releasing every small fix individually. Many small commits become one well-scoped release.

Turn a cold start into a warm one. Build a single orientation document for a project, account, or workspace, what it is, where things live, the decisions made so far, the open items, and the next move, so a new session or a new teammate is productive in minutes instead of days. Trigger on "get me up to speed", "onboard someone to this", "what's the context here", "brief a new session", "orient me on this account", or any cold-start on work already in motion.

Automates semantic versioning and release workflow for Claude Code plugins, including version increments across multiple manifest files, build verification, git tagging, GitHub releases, and changelog generation.

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

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