ワンクリックでManusで任意のスキルを実行

es-x-snapshot-config-update

スター155

フォーク13

更新日2026年7月4日 03:04

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

eslint-community

eslint-community/eslint-plugin-es-x

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

ES-X Snapshot Config Update

Workflow

Use this in the eslint-plugin-es-x repository when a yearly ECMAScript snapshot has become the latest stable snapshot. Keep this work separate from Node.js support drops and ESLint support drops unless the user explicitly asks for a combined PR.

Confirm the repo is clean enough to work with git status --short.
Inspect scripts/rules.ts and find LATEST_ES_YEAR.
Change LATEST_ES_YEAR to the new stable snapshot year. This is the one manual source edit.
Run npm run update.
Review generated changes:
- New lib/configs/no-new-in-esYYYY.js and lib/configs/flat/no-new-in-esYYYY.js.
- New restrict-to-es{YYYY-1} legacy and flat configs.
- no-new-in-esnext* should now contain only post-YYYY rules; it may become empty for Intl API.
- lib/index.ts should expose the new config keys and types.
- docs/configs/index.md, docs/rules/index.md, and affected rule docs should link to the stable config names.
Add release notes for this snapshot-config PR through .agents/es-x-changeset/SKILL.md.
Verify this snapshot-config PR through .agents/es-x-release-verification/SKILL.md.

Project Notes

Do not hand-edit generated config or docs files unless the generator is wrong. The source of truth is scripts/rules.ts plus rule metadata in lib/rules/*.

The README policy says major releases update configs when new ECMAScript snapshots are available. Proposal-specific configs stop showing the experimental warning once their category is no longer experimental.

When checking the diff, look for ESYYYY rules moving from no-new-in-esnext to no-new-in-esYYYY, and for older restrict-to-* configs extending or merging the new stable year.

このリポジトリの他の Skills

同じリポジトリ

es-x-eslint-support-update

eslint-community/eslint-plugin-es-x

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.

2026-07-04155

es-x-node-support-update

eslint-community/eslint-plugin-es-x

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.

2026-07-04155

es-x-changeset

eslint-community/eslint-plugin-es-x

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.

2026-07-04155

es-x-major-version-prep

eslint-community/eslint-plugin-es-x

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.

2026-07-04155

es-x-release-verification

eslint-community/eslint-plugin-es-x

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.

2026-07-04155

name	es-x-snapshot-config-update
description	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.

ES-X Snapshot Config Update

Workflow

Confirm the repo is clean enough to work with git status --short.
Inspect scripts/rules.ts and find LATEST_ES_YEAR.
Change LATEST_ES_YEAR to the new stable snapshot year. This is the one manual source edit.
Run npm run update.
Review generated changes:
- New lib/configs/no-new-in-esYYYY.js and lib/configs/flat/no-new-in-esYYYY.js.
- New restrict-to-es{YYYY-1} legacy and flat configs.
- no-new-in-esnext* should now contain only post-YYYY rules; it may become empty for Intl API.
- lib/index.ts should expose the new config keys and types.
- docs/configs/index.md, docs/rules/index.md, and affected rule docs should link to the stable config names.
Add release notes for this snapshot-config PR through .agents/es-x-changeset/SKILL.md.
Verify this snapshot-config PR through .agents/es-x-release-verification/SKILL.md.

Project Notes

Do not hand-edit generated config or docs files unless the generator is wrong. The source of truth is scripts/rules.ts plus rule metadata in lib/rules/*.

When checking the diff, look for ESYYYY rules moving from no-new-in-esnext to no-new-in-esYYYY, and for older restrict-to-* configs extending or merging the new stable year.