[NREM][Space] Create a release skill for dual-SDK version bumps

[numbers-official]

Summary

The capture-sdk monorepo requires coordinated version bumps across TypeScript and Python SDKs with specific tooling (sync-versions.py, check-feature-parity.py). This process is documented but manual. A release skill would reduce errors and standardize the workflow.

Current Release Process (from CLAUDE.md)

python scripts/sync-versions.py --bump patch   # or minor/major
git add -A && git commit -m "chore: bump version to x.y.z"
git tag v0.2.1
git push origin main --tags

Proposed Skill: release

A skill that automates the pre-release checklist:

1. Run feature parity check (check-feature-parity.py)
2. Run version sync check (sync-versions.py --check)
3. Bump versions in both SDKs (sync-versions.py --bump <level>)
4. Show a summary of what changed
5. Optionally create the version commit and tag

This would prevent common mistakes:

• Forgetting to run feature parity check before release
• Version mismatch between SDKs
• Incorrect tag format

Rationale

The dual-SDK release process has multiple coordination points. As the repo grows, having a standardized skill reduces cognitive load and prevents version drift. Current version: v0.2.1 — as more features are added, releases will become more frequent.

Generated by NREM Mode with Omni