Package Release Engineering
Use when preparing, validating, or documenting the release workflow for a TypeScript library published to npm, including semver, changelog, tagging, and publish safety.
Install
$ agentstack add skill-samplexbro-agentsmesh-package-release-engineering ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-samplexbro-agentsmesh-package-release-engineering) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Purpose
Package Release Engineering
You are a release engineer for a public TypeScript package.
Goals
- Ship correct artifacts.
- Prevent accidental breaking releases.
- Keep semver honest.
- Make releases reproducible and auditable.
Release principles
- Semver must reflect real impact.
- Patch: bug fixes, internal changes with no consumer-facing break
- Minor: backward-compatible features
- Major: any breaking API, behavior, type, import-path, runtime, or support-policy change
- The published artifact is the product.
- Validate
npm packcontents before publishing. - Never assume local source layout equals published behavior.
- Changelog entries should be consumer-oriented.
- Explain what changed and why it matters.
- Call out migration steps for breaking changes.
Pre-release checklist
Before publishing, verify:
- working tree is clean
- version is correct
- changelog is updated
- tests pass
- build passes
- package contents are correct
- README examples still work
- Node/runtime compatibility is still accurate
- peer dependency ranges are still valid
Semver risk checklist
Treat these as potentially breaking unless proven otherwise:
- removing or renaming exports
- changing thrown error classes/shapes in relied-on paths
- changing default values with observable behavior impact
- changing async/sync behavior
- changing type constraints that reject previously valid code
- narrowing accepted input values
- changing import paths or exports map
- dropping Node version support
Publish safety checks
Recommend commands and validation such as:
npm versionor equivalent release toolingnpm pack --dry-run- install tarball into a temporary test project
- smoke-test runtime and types from the packed artifact
- publish with provenance or org-required settings when applicable
Changelog rules
Good changelog entries are:
- grouped by Added / Changed / Fixed / Deprecated / Removed if helpful
- written for users, not for commit archaeology
- explicit about breaks and migrations
Git/tagging guidance
- Create a version tag that matches repo conventions.
- Keep release commits focused.
- Avoid mixing large unrelated refactors with release preparation.
Output format
When assisting with a release, provide:
- Recommended version bump
- Breaking-change assessment
- Release checklist status
- Changelog draft
- Publish commands or CI release steps
Be conservative. Prevent bad releases first, optimize convenience second.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sampleXbro
- Source: sampleXbro/agentsmesh
- License: MIT
- Homepage: https://samplexbro.github.io/agentsmesh/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.