メニュー
Create release notes that summarize features, fixes, and migration guidance for software releases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | release-notes-generator |
| description | Create release notes that summarize features, fixes, and migration guidance for software releases. |
Create release notes summarizing features, fixes, and breaking changes for releases.
Use this skill when you need to:
# Release v1.2.0
## Highlights
Brief summary of the most important changes (2-3 sentences).
## New Features
### Feature Name
Description of what it does and why it matters.
**Usage:**
```typescript
// Code example
What changed: Description
Migration:
// Before
oldMethod();
// After
newMethod();
package-name from 1.0.0 to 2.0.0
## Information Gathering
### Git Commands
```bash
# Commits since last release
git log v1.1.0..HEAD --oneline
# Detailed commit messages
git log v1.1.0..HEAD --format="%h %s%n%b%n---"
# Files changed
git diff v1.1.0..HEAD --stat
# Contributors
git log v1.1.0..HEAD --format="%an" | sort | uniq
Focus on user value:
Include:
Must include:
Follow semantic versioning:
# Release v1.2.0
## Highlights
This release adds health data visualization and improves task scheduling
performance. Users can now view their health trends over time.
## New Features
### Health Data Visualization
View your health metrics in interactive charts.
**Usage:**
```typescript
import { HealthChart } from './components/health';
<HealthChart data={healthData} timeRange="week" />
What changed: useHealthData() now returns an object instead of array
Migration:
// Before
const [data, isLoading] = useHealthData();
// After
const { data, isLoading } = useHealthData();
## Checklist
- [ ] Highlights summarize key changes
- [ ] All new features documented with examples
- [ ] Breaking changes have migration guides
- [ ] Bug fixes reference issue numbers
- [ ] Version number follows semver
Turn planning outputs into a milestone-based implementation plan that sequences features, maps them to available packages or modules, and hands off to a coding agent for implementation.
Walk through the full process of building a digital health app — from planning to implementation.
Choose between React Native and Apple-native for a digital health app, clone the matching Spezi starter template, and move existing planning briefs into the cloned repo so the coding agent has full context for implementation.
Set up and maintain a persistent, LLM-managed knowledge base for a digital health project — turning clinical observations, papers, interviews, and planning docs into a compounding, interlinked wiki.
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
Plan healthcare privacy, research, and regulatory compliance for a digital health product, including HIPAA, IRB, FDA, GDPR, governance, and operational controls.