contentstack/kickstart-next · Archived

dev-workflow

Local setup, Contentstack seeding, env vars, CI expectations, and PR ownership for kickstart-next.

First seen Jun 17, 2026

Installation

$ npx skills add contentstack/kickstart-next --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/kickstart-next.

npx skills add contentstack/kickstart-next

Browse all from contentstack/kickstart-next

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 2
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,289 B
  • docs SUMMARY.md 118 B

History

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

SKILL.md

Dev workflow – kickstart-next

When to use

  • You are cloning the repo, running it locally, or opening a pull request.
  • You need to know what runs in CI versus what you must run locally.

Instructions

Local setup

  • Install dependencies with npm install.
  • Copy .env.example to .env and fill in values from your Contentstack stack (see product [README.md](../../README.md)).
  • Required variables use the NEXTPUBLICCONTENTSTACK_* prefix; see .env.example for names.

Contentstack stack

  • Install the Contentstack CLI (npm install -g @contentstack/cli), configure region if prompted, and log in (csdx auth:login).
  • Seed a compatible stack: csdx cm:stacks:seed --repo "contentstack/kickstart-stack-seed" --org "<YOURORGID>" -n "Kickstart Stack" (details in [README.md](../../README.md)).
  • Create a delivery token with preview scope and preview token enabled; enable Live Preview in the stack and point it at the Preview environment.

Run the app

  • Development: npm run dev, then open http://localhost:3000.
  • Production build locally: npm run build then npm run start.

Lint

  • Run npm run lint before pushing; there is no GitHub Actions workflow that runs ESLint for this repo.

CI (GitHub Actions)

  • [.github/workflows/sca-scan.yml](../../.github/workflows/sca-scan.yml): Snyk and contentstack/sca-policy on pull requests.
  • [.github/workflows/policy-scan.yml](../../.github/workflows/policy-scan.yml): checks for SECURITY.md and license/year for public repos.
  • [.github/workflows/issues-jira.yml](../../.github/workflows/issues-jira.yml): issue integration.
  • There is no workflow that runs npm run build or npm run lint in CI; treat those as developer responsibilities unless a workflow is added later.

CODEOWNERS

  • Default reviewers: @contentstack/devex-pr-reviewers (see [.github/CODEOWNERS](../../.github/CODEOWNERS)).
  • Security workflows and related paths may require @contentstack/security-admin.

Optional: Talisman

  • A [.talismanrc](../../.talismanrc) file exists; follow your org’s guidance if Talisman is used locally for secret scanning.