菜单
Generate release notes from git history, pull request descriptions, and changelog entries. Use when preparing a release, summarizing changes for stakeholders, or updating a CHANGELOG file.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Summarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.
Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.
Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.
Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.
Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.
Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.
| name | drafting-release-notes |
| description | Generate release notes from git history, pull request descriptions, and changelog entries. Use when preparing a release, summarizing changes for stakeholders, or updating a CHANGELOG file. |
Generate clear, audience-appropriate release notes by analyzing the changes between two reference points (tags, branches, or commits).
Gather changes — collect commits, merged PRs, and closed issues between the two reference points.
Categorize — group changes into standard sections:
Summarize each entry — write one concise line per change that describes the user-facing impact, not the implementation detail. Reference the PR or issue number.
Highlight breaking changes — call out anything that requires user action (API changes, config format changes, removed features) in a dedicated section at the top.
Add context — include upgrade instructions for breaking changes and link to relevant documentation or migration guides.
Follow Keep a Changelog conventions:
## [version] - YYYY-MM-DD
### Breaking Changes
- Description of breaking change (#PR)
### Added
- Description of new feature (#PR)
### Fixed
- Description of bug fix (#PR)