القائمة
Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when wanting to systematically improve the React/TypeScript frontend - scans for security vulnerabilities, stability risks, performance issues, and code simplification opportunities, then presents 5 ranked findings for the user to choose from
Add support for a Kubernetes resource type by choosing the required catalog, refresh, detail, object-map, permission, frontend, docs, and test surfaces
Guide for safely modifying the refresh/streaming subsystem — covers the full domain lifecycle, registration points, and known fragility areas
Use when eliminating representable-but-invalid states in Luxury Yacht — converting boolean flag-soup to discriminated unions, making required identity fields non-optional, replacing stringly-typed states with literal/typed enums, and pushing scattered runtime guards into the type system or a single chokepoint. Triggers — "make impossible states impossible", flag soup (isLoading/isError/isEmpty), contradictory nullable fields, kind-only/name-only object refs, stringly-typed status, or the docs/todo.md item of the same name.
Work on Luxury Yacht object-panel details, YAML, actions, logs, shell/debug tabs, docked panels, related objects, and tests
Use for large-scale structural Luxury Yacht app reviews that audit broad systems or cross-cutting concerns, identify major simplification, hardening, optimization, or refactoring opportunities, and optionally write temporary phased plans in docs/plans
| name | draft-release-notes |
| description | Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions |
Generate formatted release notes by reading commits since the last git tag.
/draft-release-notes — generate notes from the last tag to HEAD
/release-notes <from-tag> — generate notes from a specific tag to HEAD
/release-notes <from-tag> <to-tag> — generate notes between two tags
Determine range. If no arguments, find the latest tag with git tag --sort=-v:refname | head -1 and use <latest-tag>..HEAD. If arguments provided, use those.
Read commits. Run git log <range> --oneline --no-merges to get the commit list. Also run git log <range> --oneline --merges to capture PR merge commits (these have the PR title and number).
Read changed code when needed. For commits with unclear messages, read the actual changed files (git show <sha> --stat then read key files) to understand what the change does from a user's perspective.
Categorize. Group changes using Keep a Changelog types. Only include categories that have entries:
Format output. Use this template:
## v<version> — <YYYY-MM-DD>
**Added:**
- Description of feature
- Sub-detail of feature if it has multiple notable parts
**Changed:**
- Description of change
**Fixed:**
- Description of fix
Follow the conventions established in existing releases:
**Added:**, **Fixed:** — not markdown headers for categories.