release

Verify release readiness gates across quality, security, documentation, and pipeline health.

18|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/nexus-substrate/nexus-agents --skill release-nexus-substrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/nexus-substrate/nexus-agents/tree/main/skills/release
Command: npx skills add https://github.com/nexus-substrate/nexus-agents --skill release-nexus-substrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or risky releases by enforcing a consistent, production-grade checklist covering quality, security, documentation, and pipeline readiness.

Core Features & Use Cases

  • Release readiness gates: Verifies linting, typing, tests, coverage thresholds, and the absence of unresolved TODO/FIXME/debugging artifacts before tagging.
  • Security and dependency hygiene: Requires clean audit and scanning results and flags vulnerability or credential issues before publishing.
  • Governance and doc drift control: Ensures generated governance/documentation artifacts are in sync so published behavior matches declared rules.
  • Release workflow orchestration: Guides changesets-driven versioning, GitHub Actions publishing (OIDC trusted publishing), and emergency/manual publishing and rollback steps.

Quick Start

Ask the AI to run the release pre-launch checklist and then confirm the correct changesets-based release workflow steps are ready to execute on main.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publishing with GitHub Actions and changesets?

Automate npm publishing by using a changesets-driven workflow with GitHub Actions OIDC trusted publishing, which verifies readiness gates across quality, security, and documentation before tagging and deploying.

What's the best way to prevent broken npm releases in CI pipelines?

Prevent broken npm releases by enforcing CI gates that require clean pnpm lint, typecheck, test results, and vulnerability scans before executing changesets versioning and publishing.

How do I validate release readiness before tagging a version?

Validate release readiness by running a pre-launch checklist that checks for unresolved TODO/FIXME artifacts, verifies governance documentation sync, and confirms pipeline health before tagging.

Does OIDC trusted publishing work with changesets for npm versioning?

OIDC trusted publishing works with changesets by orchestrating GitHub Actions release workflows that include race-condition safeguards and validate security audits before deploying.

Why do my changesets releases fail due to governance or doc drift?

Changesets releases fail due to doc drift when generated governance artifacts are out of sync, meaning published behavior would not match declared rules and failing the release readiness gates.

Can I do an emergency npm publish bypassing standard CI gates?

Emergency npm publishing is supported through manual publishing and rollback steps within the repository's release workflow, bypassing standard gates while maintaining audit and scanning oversight.