メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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".
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 | pr-checklist |
| description | 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. |
Run through this before opening a pull request. Report each item's result; don't silently skip failures.
main/master.git status — no unintended files staged (build output, .env, editor junk, lockfile churn from an unrelated package manager).Run whichever exist in the repo (check package.json scripts first):
tsc --noEmit or the repo's typecheck script)lint script)test script)build script) — for app repos, confirm it completesIf a gate fails, fix it or stop and report — never open the PR with known-failing gates without the user's explicit OK.
Read the full diff (git diff <default-branch>...HEAD) looking for:
console.log, commented-out blocks, TODOs added by this branch.env.exampleCHANGELOG.md if the repo keeps one (use the changelog-update skill).Draft with this shape:
## What
One or two sentences: the change from the user's/reviewer's perspective.
## Why
The problem or requirement driving it. Link the issue if one exists.
## How to verify
Concrete steps a reviewer can follow to confirm it works.
Present the checklist results and the draft description before pushing, unless the user asked for the PR to be opened directly.