grafema-release

Automates version bumping, validation, and npm publishing for the Grafema project.

36|2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Disentinel/grafema --skill grafema-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafema-release
Source: https://github.com/Disentinel/grafema/tree/main/.claude/skills/grafema-release
Command: npx skills add https://github.com/Disentinel/grafema --skill grafema-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing new versions of the Grafema project to the npm registry, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Version Bumping: Automatically increments patch, minor, or major versions across all Grafema packages.
  • Pre-Release Validation: Enforces critical checks like branch status, test results, and changelog updates before publishing.
  • Binary Management: Handles the mandatory download of prebuilt binaries for the @grafema/rfdb package.
  • CI/CD Integration: Works seamlessly with GitHub Actions for automated validation and manual triggering of the publish workflow.
  • Use Case: When a new set of features is ready, you can use this Skill to initiate a beta release, ensuring all checks pass before it goes live.

Quick Start

Use the grafema-release skill to perform a patch release with publishing enabled.

Frequently Asked Questions about grafema-release

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

FAQPage Schema
How do I automate npm publishing for a multi-package project?

To automate npm publishing, this Skill handles version bumping across packages, enforces pre-release validation, and integrates with GitHub Actions to publish new releases to the npm registry.

What checks are required before publishing a beta release to npm?

Before publishing a beta release, the Skill enforces pre-release validation by checking Git branch status, verifying test results, and ensuring changelog updates are completed.

Can I use GitHub Actions to trigger a patch release workflow manually?

Yes, you can use GitHub Actions to trigger a patch release workflow manually, allowing the Skill to automate version bumping, run validation, and execute the npm publishing process.

How does CI/CD integration handle prebuilt binaries during npm releases?

During CI/CD integration, the Skill handles binary management by automatically downloading prebuilt binaries required for the rfdb package before publishing to npm.

What is the rollback procedure if an npm release fails validation?

The Skill manages rollback procedures for new beta or stable releases, ensuring that failed npm publications or validation errors can be safely reverted during the CI/CD process.

Do I need specific Git branching protocols for version bumping and publishing?

Yes, the Skill requires adherence to specific Git branching protocols and testing standards to ensure version bumping and npm publishing occur safely without breaking dependencies.