メニュー
Update CHANGELOG.md for the changes on the current branch, following Keep a Changelog format. Use when the user asks to update the changelog, prep release notes, or before opening a PR in repos that keep a changelog.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Verify an Electron app's security posture and packaging readiness before release — BrowserWindow webPreferences, preload/contextBridge surface, IPC handler validation, navigation and external-content lockdown, CSP, and electron-builder config. Use before merging changes that touch main-process code, the preload script, window creation, or packaging config — or when the user asks to "check Electron security", "audit the IPC surface", or "verify the build config".
Design and build premium, immersive frontend UI — deliberate aesthetic direction, motion design, fluid typography, and performance guardrails. Use when the user asks for a "premium", "immersive", "polished", or "Awwwards-style" page or component, or asks to elevate the visual quality of existing UI. Not for routine CRUD screens or internal tooling where plain, fast UI is the right call.
Verify a Hugo site or theme builds clean and ships correct output before release — production build with warnings-as-errors, template lookup and unused-template audit, head/SEO surface, asset pipeline (fingerprint/SRI, image processing), internal links, and publish-surface hygiene (drafts, secrets, robots). Use before merging changes that touch layouts/, assets/, config, archetypes, or shortcodes — or when the user asks to "check the theme", "verify the build", or "audit the site".
Pre-PR verification pass — run checks, review the diff, and draft the PR description. Use when the user says the work is ready for a PR, asks to open a PR, or asks for a pre-PR review.
Verify a Vite + vite-plugin-pwa app's installability and offline correctness before release — production build, manifest completeness, icon set, service-worker registration and update strategy, and caching-config safety. Use before merging changes that touch vite.config.ts PWA options, the manifest, icons, the service-worker update flow, or caching strategies — or when the user asks to "check the PWA", "verify offline", or "audit the manifest".
Create a commit message from staged changes, bump and sync version numbers, update CHANGELOG.md, and run npm run docs only when changes are not minor. Use for pre-commit finalization, version hygiene, changelog hygiene, and docs gating.
| name | changelog-update |
| description | Update CHANGELOG.md for the changes on the current branch, following Keep a Changelog format. Use when the user asks to update the changelog, prep release notes, or before opening a PR in repos that keep a changelog. |
Update CHANGELOG.md to reflect the work on the current branch.
git log --oneline <default-branch>..HEAD plus git diff --stat <default-branch>...HEAD. If the branch has no commits yet, use the staged/working changes instead.CHANGELOG.md. If it doesn't exist, create it with a # Changelog header, a note that it follows Keep a Changelog, and an ## [Unreleased] section.## [Unreleased], grouped by category — only include categories that have entries:
### Added — new features### Changed — changes to existing behavior### Fixed — bug fixes### Removed — removed features### Security — vulnerability fixes[Unreleased] until then.Rename [Unreleased] to [X.Y.Z] - YYYY-MM-DD (matching the version in package.json), and add a fresh empty [Unreleased] section above it.