skill-release-manager

Automating versioning and GitHub releases involves incrementing the version in package.json, committing changes, syncing to a remote repository, and creating a release tag. This skill handles these steps end-to-end to streamline your skill deployment workflow.

Yes, you can publish to ClawHub and create a GitHub release simultaneously. The process syncs your code to a remote repository, creates the release, and publishes the skill to the ClawHub registry in one streamlined operation.

Yes, you need the authenticated clawhub CLI and the skill-publisher dependency to automate skill releases. These tools are required to handle the end-to-end version management, Git operations, and ClawHub publishing workflows.

Automating skill deployment supports configurable version increments including patch, minor, major, or a specific version number. This ensures flexible version management when updating your package.json during the release process.

You can add custom release notes when publishing a skill to ClawHub by providing them during the release process. The automation uses these notes when creating the GitHub release and pushing the updated version to the registry.

Automated release management requires Git operations to commit version changes locally and sync them to a remote repository. This ensures the codebase and GitHub release tags remain consistent with the published ClawHub skill version.