contentstack/contentstack-management-javascript · Archived

dev-workflow

Branches, lint/tests before PR, semver version bumps, and PR expectations for contentstack-management-javascript.

First seen Jul 16, 2026

Installation

$ npx skills add contentstack/contentstack-management-javascript --skill dev-workflow

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from contentstack/contentstack-management-javascript.

npx skills add contentstack/contentstack-management-javascript

Browse all from contentstack/contentstack-management-javascript

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,865 B
  • docs SUMMARY.md 133 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Development workflow – Contentstack Management JavaScript SDK

When to use

  • Starting work or opening a PR.
  • Choosing which npm scripts to run before push.
  • Deciding whether to bump package.json version.

Instructions

Branches

  • Follow team Git conventions (e.g. feature branches off development / integration branch used in this repo).
  • Keep commits focused; do not commit with test.only, it.only, describe.only, or permanent skips.

Before opening a PR

  1. npm run lint — ESLint must pass on lib and test.
  2. Unit tests — npm run test:unit. (npm test also runs test:api first — confirm test:api is defined in package.json on your branch.)
  3. Sanity / API tests — only when validating against live CMA: npm run build then npm run test:sanity-nocov or test:sanity-test, with env vars per test/sanity-check/utility/testSetup.js. Never commit secrets.
  4. Version bump — For user-visible or release-worthy lib/ changes (new API, shipped fix, breaking change), update version in package.json per semver (patch / minor / major). Docs-only or chore-only PRs may omit per team practice.

PR expectations (summary)

  • User-facing changes — JSDoc on public methods; update types/** when the public surface changes.
  • Behavior — Preserve backward compatibility unless the change is explicitly breaking and documented.
  • Errors — Use lib/core/contentstackError.js patterns; do not leak full tokens in logs.
  • Tests — Unit tests under test/unit/ with mocks; for sanity env and commands, use the testing skill (listed in AGENTS.md).