# Node Package Release Engineering

> Use this skill for npm package exports, ESM/CJS compatibility, semantic versioning, release automation, changelogs. Trigger when the task involves programming work related to Node Package Release Engineering, implementation, audits, debugging, strategy, or validation.

- Skill: `srednoff888-art/node-package-release-engineering` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add srednoff888-art/node-package-release-engineering`
- Raw SKILL.md: https://api.skillmd.com/api/skills/srednoff888-art/node-package-release-engineering/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: srednoff888-art (https://skillmd.com/u/srednoff888-art)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/srednoff888-art/node-package-release-engineering

---


# Node Package Release Engineering

Use this skill for Programming tasks focused on npm package exports, ESM/CJS compatibility, semantic versioning, release automation, changelogs.

## Workflow

1. Clarify the user outcome, constraints, current stack, and definition of done.
2. Inspect local source, artifacts, analytics exports, logs, designs, or docs before changing anything.
3. Check official documentation when APIs, SDKs, policies, search behavior, accessibility rules, or production behavior may have changed.
4. Compare proven open-source patterns for non-trivial choices and adapt ideas without copying incompatible code.
5. Produce the smallest production-ready change or recommendation that satisfies the request.
6. Validate with relevant evidence: tests, lint, typecheck, build, screenshots, crawl output, logs, analytics, or manual scenario.
7. Report commands, files, findings, risks, and next steps clearly.

## Focus Checklist

- Map inputs, owners, dependencies, and constraints.
- Prefer existing project conventions, design systems, and platform primitives.
- Include failure states, privacy/security implications, performance impact, and rollback where relevant.
- Separate facts from assumptions and mark any unverified claims.
- Keep recommendations actionable and prioritized by impact and risk.

## Guardrails

- Do not publish or tag releases without explicit confirmation.
- Do not perform destructive, paid, production, publishing, account-changing, or externally visible actions without explicit user confirmation.
- Do not expose secrets, private keys, tokens, cookies, private analytics, personal data, or confidential business data.
- If validation is impossible, state why and provide a concrete manual verification path.