Menü
PR and release checklist for cli-cm-regex-validate (security, packaging, CI, messages)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Contentstack CLI plugin patterns for cm:stacks:validate-regex (SDK, schema, safe-regex, output)
Local and CI workflow for cli-cm-regex-validate — commands, layout, naming, hooks, and merge expectations
Jest testing patterns for cli-cm-regex-validate (mocks, fixtures, no live API calls)
Reviews pull requests and risky changes for the contentstack-cli-content-type plugin. Use when reviewing diffs, security-sensitive edits, dependency upgrades, or changes to compare/diagram/temp-file behavior, ESLint, and tests.
Develops and maintains the contentstack-cli-content-type csdx plugin (content-type list, details, audit, compare, compare-remote, diagram). Use when editing this repository, ContentTypeCommand setup and flags, CMA/Management SDK usage, axios audit/references calls, diff/compare HTML output, Graphviz diagrams, or oclif readme/manifest workflows.
Local build, test, lint, coverage, TypeScript layout, ESLint, and oclif-generated docs for contentstack-cli-content-type. Use when changing package.json scripts, tsconfig, .eslintrc, Jest config, README/oclif manifest, or validating before a PR.
| name | code-review |
| description | PR and release checklist for cli-cm-regex-validate (security, packaging, CI, messages) |
npm test only; see AGENTS.md); no secrets in commits; plugin files and prepack remain consistent; workflows aligned with Node version used in CI.Open skills/code-review/ when reviewing PRs or before release (or point your agent at this folder if supported).
cm:stacks:validate-regex (flags, prompts, stack connection, CT/GF selection).messages/index.json under validateRegex (avoid hard-coded copy in production paths).npm test passes locally.test/utils/ tests and/or test/data/ fixtures where appropriate.posttest or project eslint script). Note: CI does not run ESLint — only npm test in .github/workflows/unit-tests.yml; lint must pass locally before merge.strict and project conventions (see tsconfig.json, .eslintrc, and AGENTS.md).package.json files includes what ships (lib, bin, oclif.manifest.json, messages, etc.).prepack still runs tsc, oclif manifest, and oclif readme as needed for the plugin.main) matches .github/workflows/release.yml expectations.npm test on a supported Node version (see .github/workflows/unit-tests.yml). Expect Jest only there — not posttest/ESLint unless you add a separate workflow.