Menu
Use when writing changelog entries, release notes, or customer-facing "what's new" from features, commits, or a feature list. Not for internal code review or marketing landing page copy from scratch.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when reviewing or fixing accessibility: keyboard navigation, focus order, labels, color contrast, screen reader support, or ARIA attributes. Not for SEO-only or performance-only audits.
Use when adding product analytics (PostHog, GA4, Plausible), event tracking, funnels, or conversion measurement. Not for server logs only or A/B infra unless events are part of the task.
Use when standardizing API and edge function errors: HTTP status codes, error JSON shape, logging, or mapping Supabase/Stripe errors to client responses. Not for UI toast copy only or form field validation messages.
Use when recording audit trails: who changed what, admin action logs, compliance history, or append-only event tables. Not for product analytics (use analytics-events) or debug console logs only.
Use when scheduling background work: cron jobs, digest emails, cleanup tasks, pg_cron, Supabase scheduled edge functions, or job queues. Not for synchronous user-facing API in the request path.
Use when adding dark mode, theme toggle, system theme support, or fixing hardcoded colors that break in dark mode. Not for design-token migration unrelated to dark mode.
| name | release-notes |
| description | Use when writing changelog entries, release notes, or customer-facing "what's new" from features, commits, or a feature list. Not for internal code review or marketing landing page copy from scratch. |
Ask or infer: end users (simple, benefit-led) vs developers (technical).
Default: end users unless stated otherwise.
# v1.4.0 — May 22, 2026
## Highlights
- One sentence theme of the release.
## New
- Feature — why it matters.
## Improved
- Change — user-visible benefit.
## Fixed
- Bug — what was broken.
## Breaking (if any)
- What changed + migration step.
From vague prompts, extract discrete shippable items. Do not invent features not described.