القائمة
Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Consult a stronger model mid-task for a second opinion before committing to an approach, when stuck, or before declaring a non-trivial task done — the fast-executor + strong-advisor pattern, implemented with the Agent and Workflow tools (Claude Code does not expose Anthropic's raw API advisor tool). Use when running on a cheaper/faster model for mechanical work and a hard design/architecture/risk decision needs a stronger check, or when authoring a Workflow script that should get expert review partway through instead of only at the end.
Use when the user says "caveman mode", "talk like caveman", "use caveman", "less tokens", or "be brief", invokes /caveman, or when token efficiency is requested. Switches responses to an ultra-compressed terse style (multiple intensity levels available, ~75% token reduction) while preserving full technical accuracy.
Use right after being corrected on something a CLAUDE.md file should already have told you, when explicitly asked to review CLAUDE.md, or periodically after a session with a lot of back-and-forth — reviews THIS conversation for friction and proposes a bounded CLAUDE.md edit. A lightweight, single-session complement to skill-tuning-loop (which mines many sessions and validates a proposal against held-out cases before surfacing it — reach for that instead when the ask is "make this systematic," not "check right now"). Own version of the dx plugin's `/dx:review-claudemd`.
Generate a solution, evaluate it against explicit pass/fail criteria, refine using the feedback, repeat until it passes or a round cap is hit. Use for tasks with a clear, checkable bar and demonstrable value from iteration — a bug fix that must pass a test suite, code that must satisfy a lint/style rubric, a document that must meet stated requirements. Distinct from advisor-checkpoint (one strategic consult before committing) — this is a convergence loop against a concrete standard.
Use when PR checks fail, CI is red, or GitHub Actions workflows break - systematically inspects failing checks via gh CLI, pulls logs, checks for flakiness and scopes the breaking commit, scopes external checks, then creates fix plan using existing plan skill
Write a structured handoff document before a session ends, before a context-heavy interruption (SSH/tmux disconnect, context running low, a worktree being handed to another worker or agent), or when explicitly asked for a handoff — captures progress, what worked/failed, and the exact next step so a fresh session can resume without re-deriving context. Own version of the dx plugin's `/dx:handoff`.
| name | release-app-store-changelog |
| description | Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags. |
Generate comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.
Get commits since the last tag:
# Find the last tag
git describe --tags --abbrev=0
# List commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# Or with more detail
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%h %s" --no-merges
If comparing specific refs:
git log v1.2.3..HEAD --oneline --no-merges
If no tags exist:
git log --oneline --no-merges -50 # Last 50 commits
Scan commits and identify user-visible changes:
Include:
Exclude:
Group changes by theme:
Write short, benefit-focused bullets:
Language guidance:
Examples:
What's New
• Added [feature description]
• Improved [enhancement description]
• Fixed [bug fix description]
Or with sections:
What's New in [Version]
New
• [Feature 1]
• [Feature 2]
Improved
• [Enhancement 1]
Fixed
• [Bug fix 1]
• [Bug fix 2]
# Full workflow: commits since last tag with files changed
git log $(git describe --tags --abbrev=0)..HEAD --stat --no-merges
# Just commit messages
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"- %s" --no-merges
# List all tags
git tag -l --sort=-v:refname
# Compare two specific tags
git log v1.1.0..v1.2.0 --oneline --no-merges