Back to Details

log

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Changelog Logger

变更日志记录器

Log completed epics using the following template in reverse chronological order:
undefined
按照以下模板，以时间倒序记录已完成的Epic：
undefined

$date

$date

  • $emoji - $epicName - $briefDescription

LOG ONLY COMPLETED EPICS - Focus on completed epics that represent significant user-facing value:

- Epic Completions: Major feature releases, tool creation, system implementations
- User-Impacting Changes: New capabilities, workflows, or developer experience improvements
- Architecture Decisions: Significant refactoring, new patterns, or system redesigns

DO NOT LOG: Config file changes, file organization/moves, minor bug fixes, documentation updates, dependency updates, internal refactoring, test additions/changes, meta-work.
  • $emoji - $epicName - $briefDescription

仅记录已完成的Epic - 聚焦于能为用户带来显著价值的已完成Epic：

- Epic完成项：重大功能发布、工具创建、系统实现
- 用户影响变更：新功能、工作流或开发者体验优化
- 架构决策：重大重构、新模式或系统重新设计

请勿记录：配置文件变更、文件整理/移动、小bug修复、文档更新、依赖更新、内部重构、测试新增/变更、元工作。

Emojis

表情符号说明

🚀 new feature | 🐛 bug fix | 📝 documentation | 🔄 refactor | 📦 dependency update | 🎨 design | 📱 UI/UX | 📊 analytics | 🔒 security
🚀 新功能 | 🐛 bug修复 | 📝 文档 | 🔄 重构 | 📦 依赖更新 | 🎨 设计 | 📱 UI/UX | 📊 数据分析 | 🔒 安全

Rules

规则

  • Always use reverse chronological order (most recent first).
  • Keep descriptions brief (< 50 chars).
  • Focus on epic-level accomplishments, not implementation details.
  • Never log meta-work or trivial changes.
  • Omit the "epic" from the description.
Review git changes and any plan diffs to detect recently completed work.
  • 始终使用时间倒序（最新的在前）。
  • 描述保持简洁（少于50个字符）。
  • 聚焦于Epic级别的成果，而非实现细节。
  • 切勿记录元工作或琐碎变更。
  • 描述中省略“epic”一词。
查看Git变更和任何计划差异，以发现近期完成的工作。