Back to Details

weekly-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Weekly review

每周回顾

Trigger

触发场景

Need a weekly recap of shipped work for status updates, retros, or planning.
需要每周汇总已交付工作，用于状态更新、回顾会议或规划。

Workflow

工作流程

  1. Determine the current git user email from repo config.
  2. Collect authored commits from the last 7-10 days on the primary branch context.
  3. Exclude merge commits.
  4. Group meaningful changes into 2-5 concise bullets.
  5. Add a short classification paragraph covering:
    • likely bug fixes
    • likely tech debt work
    • likely net-new functionality
  1. 从仓库配置中获取当前 git 用户邮箱。
  2. 在主分支环境下收集过去7-10天内由本人提交的 commits。
  3. 排除 merge commits。
  4. 将有意义的变更整理为2-5条简洁的要点。
  5. 添加一段简短的分类说明，涵盖：
    • 疑似 bug 修复
    • 疑似技术债务处理
    • 疑似新增功能

Guardrails

约束规则

  • Keep the recap short and executive-readable.
  • Base claims only on commit history and diffs.
  • If git email is missing, ask the user to set it before proceeding.
  • 汇总内容需简洁，适合管理层阅读。
  • 仅基于提交历史和代码差异得出结论。
  • 如果 git 邮箱缺失，请先要求用户设置后再继续。

Output

输出内容

  • 2-5 bullet weekly summary
  • Brief classification paragraph (bugfix / tech debt / net-new)
  • 2-5条要点式每周总结
  • 简短的分类说明段落（bugfix / 技术债务 / 新增功能）