Menu
Curate, update, or audit `CHANGELOG.md` in autodarts-xconfig. Use only when changelog editing, release notes, compare-link maintenance, or changelog consistency checks are explicitly in scope.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Package or verify an autodarts-xconfig userscript release. Use only for explicit release, finalize, package, ship, publish, version bump, `dist/` refresh, or publication-state verification work. Do not use for ordinary code changes.
Use for explicit SonarQube issue cleanup, Sonar code smells, low-risk static-analysis fixes, and touched-scope Sonar remediation. Do not use for normal validation unless cleanup is explicitly requested.
Use for live browser, DOM inspection, Playwright MCP, Chrome DevTools MCP, Autodarts page inspection, reproduction, console/network checks, and UI verification tasks. Do not use for ordinary static code review.
Choose and report the smallest sufficient local validation for an autodarts-xconfig change. Use after meaningful source changes, when validation scope is unclear, or when final reporting must include residual risk. Do not use for Tier 0-only edits unless needed to document skipped validation.
Recover known-good behavior from `.oldrepo` without reintroducing the old structure. Use when the current modular implementation diverges from proven legacy behavior and the task is to recover that behavior in the right modern layer. Do not use for greenfield features with no legacy predecessor.
Use when adding, fixing, or reviewing xConfig administration previews for feature effects, especially hover/focus previews that must reflect the real runtime effect without leaking timers, classes, DOM state, or fake CSS-only behavior.
| name | maintain-changelog |
| description | Curate, update, or audit `CHANGELOG.md` in autodarts-xconfig. Use only when changelog editing, release notes, compare-link maintenance, or changelog consistency checks are explicitly in scope. |
Keep CHANGELOG.md accurate, curated, and synchronized with repository truth.
CHANGELOG.md as curated human-written historyYYYY-MM-DD) for released versionsNutzerwirkung: ... and Technik: ...dist/**, and publication work to $package-userscript-releasesrc/** review unless needed to understand a changelog entrydist/** unless release packaging explicitly requires itgit status --short, git diff --name-only HEAD, relevant git log --oneline, package.json, and CHANGELOG.md.Unreleased staging section.CHANGELOG.md untouched for purely internal cleanup with no shipped or maintainer-visible effect.npm run check:changelog when changelog structure, release notes, compare links, or version parity are relevant.A valid result must:
CHANGELOG.md readable on GitHub