npm-releaselisted

# NPM Release Workflow ## Overview Standardized release process for cc-devflow npm package ensuring consistent versioning, changelog maintenance, and safe publishing. **Core Principle**: Atomic release - all version markers (package.json, CHANGELOG.md, git tag) must stay in sync. ## When to Use Use this skill when: - ✅ Ready to release a new version of cc-devflow - ✅ All changes committed and pushed - ✅ On main branch with clean working directory - ✅ Need to publish to npm registry Don't use when: - ❌ Working directory has uncommitted changes - ❌ Not on main branch - ❌ Pre-release/beta versions (needs adaptation) ## Release Types Follow [Semantic Versioning](https://semver.org/): | Type | Version Change | When | |------|---------------|------| | **Patch** | 2.4.3 → 2.4.4 | Bug fixes, minor improvements | | **Minor** | 2.4.4 → 2.5.0 | New features, backward compatible | | **Major** | 2.5.0 → 3.0.0 | Breaking changes | ## Complete Workflow ### Phase 1: Pre-Release Checks ```bash # 1. Verify git status git status # MUST show: "On branch main", "working tree clean" # 2. Check current version cat package.json | grep version # e.g., "version": "2.4.3" # 3. Review recent changes git log --oneline -10 ``` **STOP if**: - Not on main branch - Uncommitted changes exist - Unpushed commits exist ### Phase 2: Version Updates **Step 1: Update CHANGELOG.md** Add new version section at the top (after `---`): ```markdown ## [X.Y.Z] - YYYY-MM-DD ### 🎯 Release Title Brief d