원클릭으로 Manus에서 모든 스킬 실행

시작하기

code-review

스타2

포크12

업데이트2026년 4월 10일 09:01

PR checklist and severity guidance for kickstart-next contributions.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

contentstack

contentstack/kickstart-next

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Code review – kickstart-next

When to use

Before you open a PR or when reviewing someone else’s changes.

Instructions

Checklist

Run npm run lint and npm run build locally (CI does not run these automatically).
Preview mode: confirm components/Preview.tsx and initLivePreview still behave; production path: confirm server getPage + Page render correctly for /.
If you add or rename environment variables, update .env.example and user-facing docs where needed.
No secrets in the repo; scan diffs for accidental tokens.
Rich text paths still sanitize HTML (isomorphic-dompurify) before dangerouslySetInnerHTML.
If new image hosts or CDNs appear, update next.config.mjs remotePatterns (and env-driven hostname if used).
Content/schema changes should be reflected in lib/types.ts and any Live Preview $ bindings in components.
Dependency changes: consider impact on Snyk / SCA workflows (see .github/workflows).

Severity (optional labels)

Blocker: security regression (XSS, token leak), broken preview or production home route, build or lint failure.
Major: incorrect Contentstack behavior, missing env documentation, type/schema drift that can break preview editing.
Minor: style, copy, non-user-facing refactors, small UX nits.

이 저장소의 다른 Skills

같은 저장소

contentstack-kickstart

contentstack/kickstart-next

Contentstack Delivery SDK, live preview, getPage, env overrides, and content model alignment for kickstart-next.

2026-04-102

dev-workflow

contentstack/kickstart-next

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

2026-04-102

framework

contentstack/kickstart-next

Next.js, Tailwind v4, PostCSS, package scripts, and image optimization configuration for kickstart-next.

2026-04-102

next-app

contentstack/kickstart-next

App Router structure, React components, client vs server, and rendering patterns in kickstart-next.

2026-04-102

testing

contentstack/kickstart-next

Test layout and policy for kickstart-next—currently no automated tests; credentials and CI context.

2026-04-102

typescript-style

contentstack/kickstart-next

TypeScript compiler options, ESLint setup, and Contentstack entry typing conventions for kickstart-next.

2026-04-102

name	code-review
description	PR checklist and severity guidance for kickstart-next contributions.

Code review – kickstart-next

When to use

Before you open a PR or when reviewing someone else’s changes.

Instructions

Checklist

Run npm run lint and npm run build locally (CI does not run these automatically).
Preview mode: confirm components/Preview.tsx and initLivePreview still behave; production path: confirm server getPage + Page render correctly for /.
If you add or rename environment variables, update .env.example and user-facing docs where needed.
No secrets in the repo; scan diffs for accidental tokens.
Rich text paths still sanitize HTML (isomorphic-dompurify) before dangerouslySetInnerHTML.
If new image hosts or CDNs appear, update next.config.mjs remotePatterns (and env-driven hostname if used).
Content/schema changes should be reflected in lib/types.ts and any Live Preview $ bindings in components.
Dependency changes: consider impact on Snyk / SCA workflows (see .github/workflows).

Severity (optional labels)

Blocker: security regression (XSS, token leak), broken preview or production home route, build or lint failure.
Major: incorrect Contentstack behavior, missing env documentation, type/schema drift that can break preview editing.
Minor: style, copy, non-user-facing refactors, small UX nits.