package-publish

Publish retikz npm packages with synchronized versions, changelogs, and validated release workflows.

12|2|Updated Nov 27, 2024
One-click install
npx skills add https://github.com/Pionpill/retikz --skill package-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-publish
Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/package-publish
Command: npx skills add https://github.com/Pionpill/retikz --skill package-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of safely and consistently publishing retikz’s npm publishable packages while keeping the repository version, docs changelog, and roadmap tracking in sync.

Core Features & Use Cases

  • Coordinated 3-way release updates: update package versions, structured changelog data on the docs site, and roadmap checklist entries so nothing falls out of sync.
  • Release-quality validation: run lint, TypeScript type-checking, tests, builds, and npm dry-run tarball verification before any commit/tag/publish.
  • Controlled git + npm publishing flow: creates the release commit (after explicit confirmation), verifies HEAD versions, applies the correct git tag, and publishes to npm with proper dist-tag rules (alpha/beta/rc vs stable).

Quick Start

Tell the skill the target version (for example 0.1.0-alpha.1), which packages to publish (default both core and react), and the changelog text for the release, then ask it to prepare the release with confirmations.

Frequently Asked Questions about package-publish

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

FAQPage Schema
How do I publish npm packages in a monorepo while keeping the changelog and roadmap in sync?

Coordinated monorepo npm publishing synchronizes package versions, structured changelog entries, and roadmap tracking simultaneously. This ensures package versions, documentation, and roadmap checklists never fall out of sync during alpha, beta, rc, or stable releases.

How do I handle npm dist-tags for alpha, beta, and rc releases?

Npm dist-tag handling applies correct tag rules for alpha, beta, rc, and stable versions during publishing. It ensures pre-release versions get the appropriate dist-tag while stable releases use the default tag, preventing accidental installs of unstable packages.

What is the safest way to automate npm publish with git tagging?

A safe npm publish workflow runs lint, TypeScript type-checking, tests, builds, and npm dry-run tarball verification before creating any commits. After explicit confirmation, it applies the correct git tag and executes npm publish with proper registry and 2FA options.

How do I validate an npm package before publishing to the registry?

Pre-publish validation runs lint, TypeScript type-checking, tests, and builds, followed by an npm dry-run tarball inspection. This verifies the package contents and integrity before any commit, tag, or publish operation occurs.

Can I publish specific packages instead of the entire monorepo?

Yes, you can specify which monorepo packages to publish, such as targeting only @retikz/core or @retikz/react, or both by default. You provide the target version, package selection, and changelog text to prepare the release.

What are the limitations of automating release workflows with 2FA for npm?

Automated npm publishing with 2FA requires confirmed registry options and explicit confirmation before committing, tagging, and pushing. The workflow enforces deterministic working-tree edits and pre-release checks, meaning uncommitted changes or failed validations will halt the process.