release

Automate pcraft releases across npm, GitHub, and Docker via GitHub Actions.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill release-avatarganymede
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/release
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill release-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill manages release and versioning for the pcraft application, ensuring consistency across npm, GitHub, and Docker distribution channels, streamlining the release process for developers.

Core Features & Use Cases

  • Unified SemVer Management: Maintains a single Semantic Version (SemVer) for all pcraft components.
  • CI Automation: Uses GitHub Actions to automate the release process, from version bumping to GitHub release creation.
  • Platform Compatibility: Ensures releases are available on all major platforms including npm, GitHub, and Docker.
  • Use Case: When you need to cut a new release of pcraft, this Skill automates the versioning, creates a GitHub release, and publishes to npm, ensuring your release is consistent across all platforms.

Quick Start

Trigger a release by selecting 'bump' (patch/minor/major) in the GitHub Actions UI and then running the workflow.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate versioning across npm, GitHub, and Docker?

Automating versioning across npm, GitHub, and Docker is handled by maintaining a single SemVer standard and using GitHub Actions. This ensures all distribution channels receive consistent version updates during a release.

How do I trigger a new release using GitHub Actions?

Triggering a new release requires selecting the 'bump' option (patch, minor, or major) in the GitHub Actions UI and then running the workflow. This automates the version bump and subsequent publishing steps.

Does this release management approach support SemVer for all components?

Yes, this release management approach supports Semantic Versioning (SemVer) for all components. It maintains a unified SemVer standard across npm, GitHub, and Docker to ensure release consistency.

What is the best way to cut a new release for pcraft?

The best way to cut a new release for pcraft is to use this automated workflow, which handles version bumping, creates a GitHub release, and publishes to npm, ensuring consistency across all platforms.

Can I use GitHub Actions to publish to npm and Docker simultaneously?

Yes, you can use GitHub Actions to publish to npm and Docker simultaneously. The CI automation handles the release process from version bumping to GitHub release creation across all major platforms.

What are the limitations of using a single SemVer standard for multiple platforms?

Using a single SemVer standard for multiple platforms means all channels must update in lockstep. There is no support for independent platform-specific versioning, as consistency across npm, GitHub, and Docker is enforced.