القائمة
Generate changelog entries from git history using Keep a Changelog structure and user-facing release language.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | keep-a-changelog-generator |
| description | Generate changelog entries from git history using Keep a Changelog structure and user-facing release language. |
Generate changelogs from git history following Keep a Changelog format.
Use this skill when you need to:
Follow Keep a Changelog:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New features
### Changed
- Changes in existing functionality
### Deprecated
- Features that will be removed
### Removed
- Removed features
### Fixed
- Bug fixes
### Security
- Security fixes
Categorize based on commit messages and code changes:
| Category | Commit Keywords | Examples |
|---|---|---|
| Added | add, create, implement, introduce | New features, screens |
| Changed | update, change, modify, refactor, improve | API changes, enhancements |
| Deprecated | deprecate | Features to be removed |
| Removed | remove, delete, drop | Deleted features |
| Fixed | fix, resolve, correct, patch | Bug fixes |
| Security | security, vulnerability, CVE | Security patches |
# Recent commits
git log --oneline -20
# Commits between tags
git log v1.0.0..HEAD --oneline
# Full commit messages
git log --format="%h %s%n%b" HEAD~10..HEAD
# Commits since a date
git log --since="2024-01-01" --oneline
Translate technical commits to user benefits:
Flag API changes clearly:
### Changed
- **BREAKING**: `login()` now returns `Promise<User>` instead of `Promise<void>`
## [1.2.0] - 2024-01-14
### Added
- New health data visualization screen
- Apple HealthKit integration for step counting
- Export health data to PDF
### Changed
- Improved task scheduling performance
- Updated questionnaire UI design
### Fixed
- Fixed race condition in account state initialization
- Resolved infinite loop when no tasks exist
git log to get commits since last release