메뉴
Verify eslint-plugin-es-x changes before handoff or release preparation. Use after rule, config, docs, generated file, Changesets, dependency, packaging, or support-range changes to run the relevant project checks, inspect consistency, and report caveats.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Update eslint-plugin-es-x ESLint peer support in its own dedicated PR. Use during major release preparation or support policy changes to check the latest stable ESLint version and drop support for older ESLint major/minor lines by raising the minimum peer dependency without changing the Node.js engine range, updating peerDependencies, public documentation requirements, ESLint CI matrix entries, lockfile root metadata, release notes, and verification.
Update eslint-plugin-es-x Node.js support in its own dedicated PR. Use during major release preparation or support policy changes to check the current Node.js release schedule, keep the intended non-EOL Node.js lines with explicit major-line ranges, and update package engines, public documentation requirements, Node.js CI matrix entries, lockfile root metadata, release notes, and verification without changing the ESLint peer dependency.
Add or update Changesets entries for eslint-plugin-es-x. Use when a change needs release notes or a version bump, including patch fixes, minor feature/rule additions, major config changes, support-range changes, and packaging/API changes.
Prepare eslint-plugin-es-x for a major version release from a broad instruction such as "prepare the major version upgrade" or "prepare the next major release". Use to split the release-prep work into PR-sized tasks: inspect release policy and repo state, schedule old Node.js support drops and old ESLint support drops as separate PRs, decide whether the yearly ECMAScript snapshot config update is needed, regenerate generated files for one coherent task, add a major Changesets entry through the generic Changesets skill, run verification, and summarize remaining follow-up PRs.
Update eslint-plugin-es-x for a newly finalized yearly ECMAScript/ECMA-402 snapshot in its own dedicated PR. Use when preparing a major release that moves the latest snapshot year forward, updates scripts/rules.ts LATEST_ES_YEAR, regenerates no-new-in-esYYYY and restrict-to-esYYYY configs, refreshes generated docs/index files, adds task-specific release notes, and verifies this PR-sized task.
| name | es-x-release-verification |
| description | Verify eslint-plugin-es-x changes before handoff or release preparation. Use after rule, config, docs, generated file, Changesets, dependency, packaging, or support-range changes to run the relevant project checks, inspect consistency, and report caveats. |
Run the checks that match the touched surface:
git diff --checknpm test for code, rule, config, test, generated file, dependency, or broad release-prep changes.npm run build for lib, packaging, type declaration, or public API changes.npm run docs:build when docs changed.Run npm run update before verification if generated files may be stale.
Inspect the final diff for:
lib/index.ts when they are public..changeset/*.md entry exists when the change should appear in release notes.dist or coverage output are accidentally included.npm run tsc may fail because of third-party type definitions included by repo-level files even when npm run build passes. If this happens, report the exact dependency path and error separately from the verification result. Prefer npm run build as the publish-output type check because it uses tsconfig.build.json with include: ["lib"].