菜单
Use to turn a range of commits into polished, human-readable release notes grouped by theme. Delegate when preparing a GitHub release body or an announcement from a tag range, where the audience is users rather than committers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when designing memory or persistent context for an agent — deciding what to persist vs. recompute, how to retrieve only what's relevant, and how to summarize/compact history to fit the context window. Use when an agent forgets, bloats its context, or repeats work.
Interactive installer for Rosetta. Guides users through selecting and installing skills and language-specific rules at user-level or project-level, verifies paths, and optionally optimizes installed files.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills, commands, and agents.
Use when building or reviewing an evaluation for an LLM feature — assembling a representative test set, choosing pass criteria (exact match, programmatic checks, rubric, or LLM-as-judge), and catching regressions. Use when asking "how do I know this prompt or model change is better?"
Use when writing or reviewing a prompt for an LLM — making it specific, structured, and testable (clear task, role/context, examples, an explicit output contract, decomposition, room to reason) and avoiding the anti-patterns that make prompts brittle. Provider-agnostic.
Pattern for progressively refining context retrieval to solve the subagent context problem.
| name | release-notes-writer |
| description | Use to turn a range of commits into polished, human-readable release notes grouped by theme. Delegate when preparing a GitHub release body or an announcement from a tag range, where the audience is users rather than committers. |
You are a release-notes writer. You turn raw git history into release notes that a user — not a committer — wants to read.
You'll be given (or should derive) a commit range, typically <previous-tag>..<new-tag> or
<previous-tag>..HEAD.
git log <range> --pretty=format:'%h %s' and, where the
subject is terse, inspect the body with git show --no-patch <sha>.keep-a-changelog skill's format.Markdown release notes ready to paste into a release body. Concise, scannable, American English. No raw commit subjects, no SHAs in the prose (a "full changelog" link at the end is fine).