contentstack/contentstack-management-python · Archived

dev-workflow

Use for install, pytest suites, versioning, pylint, hooks, and PR baseline in contentstack-management-python.

First seen Jul 16, 2026

Installation

$ npx skills add contentstack/contentstack-management-python --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-python.

npx skills add contentstack/contentstack-management-python

Browse all from contentstack/contentstack-management-python

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 1
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,054 B
  • docs SUMMARY.md 129 B

History

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

SKILL.md

Development workflow – Contentstack Management Python

When to use

  • Setting up locally, opening a PR, or matching CI expectations.
  • Answering "how do we run tests?" or "what runs in CI?"

Instructions

Branches & releases

  • Flow: merge work to development; release PRs are development → main. After main moves, [.github/workflows/back-merge-pr.yml](../../.github/workflows/back-merge-pr.yml) can open main → development to resync.
  • PyPI: publish a GitHub Release (release: published) to run [.github/workflows/release.yml](../../.github/workflows/release.yml). PRs that touch contentstack_management/ or setup.py must bump version and CHANGELOG.md per [.github/workflows/check-version-bump.yml](../../.github/workflows/check-version-bump.yml).

Before a PR

  1. Install — pip install -e ".[dev]" then pip install -r requirements-dev.txt for linting tools.
  2. pytest tests/unit/ — required baseline (matches CI coverage run -m pytest tests/unit/).
  3. API tests — pytest tests/api/ when your change affects live CMA behavior; configure .env per tests/cred.py. Never commit tokens.
  4. Mock tests — pytest tests/mock/ when extending mocked HTTP or fixtures.

Packaging

  • Bump contentstack_management/init.py version and align setup.py versioning if release-facing.

Tooling

  • pylint is listed in requirements-dev.txt; follow existing style in touched files.
  • Husky / Talisman / Snyk — see README.md for local hook setup.

Pull requests

  • Build passes: pytest tests/unit/ at minimum; run API / mock when your change touches those layers.
  • Follow skills/code-review/SKILL.md before merge.
  • Prefer backward-compatible public API; call out breaking changes and semver.