تولیدکننده لاگ تغییرات از تاریخچه Git
Why this prompt matters
Developers write changelogs for developers. This prompt translates technical changes into user-relevant updates that actually get read.
What we use it for
Documentation
Prompt
Generate a user-facing changelog from these git commits. Group changes by: Added, Changed, Fixed, Removed. Rewrite commit messages to be understandable by end users (no technical jargon). Highlight breaking changes prominently. Include upgrade instructions for breaking changes.
Result
# v2.4.0 (2024-03-15)
## Added - Dark mode support across all pages - Export data as CSV from any table view - Keyboard shortcuts for common actions (press `?` to see all)
## Changed - Search results now update as you type (no need to press Enter) - Profile photos are now rounded instead of square
## Fixed - Fixed an issue where notifications appeared twice on mobile - Corrected timezone display for users in UTC+13/14
## Breaking Changes - **API**: The `/api/users` endpoint now returns paginated results by default. Add `?limit=0` for the previous behavior.
Developers write changelogs for developers. This prompt translates technical changes into user-relevant updates that actually get read.
This prompt demonstrates a structured approach to documentation, producing consistent, high-quality results that can be iterated upon.