contentstack/kickstart-next-ssg · Archived

testing

Test tooling status for this repo and practical notes if you introduce automated tests.

First seen Jul 16, 2026

Installation

$ npx skills add contentstack/kickstart-next-ssg --skill testing

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-ssg.

npx skills add contentstack/kickstart-next-ssg

Browse all from contentstack/kickstart-next-ssg

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

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 1,099 B
  • docs SUMMARY.md 102 B

History

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

SKILL.md

Testing – kickstart-next-ssg

When to use

  • Checking whether CI or npm runs tests (it does not, yet)
  • Planning unit, component, or E2E tests for this kickstart

Instructions

Current state

  • There is no test script in [package.json](../../package.json).
  • There are no .test., .spec., or tests directories in the repository.
  • GitHub Actions workflows do not run npm test; PR checks are security/policy focused (see [AGENTS.md](../../AGENTS.md)).

If you add tests

  • Pick a runner and add it to devDependencies and package.json scripts—do not document a framework as “already installed” until it appears in package.json.
  • Common options for this stack: Vitest or Jest with React Testing Library for components; Playwright for end-to-end flows against npm run dev.
  • Co-locate or use a tests/ (or tests/) directory and keep fixtures free of real API keys; use env files that are gitignored.