Back to Details

catchup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Table of Contents

目录

Catchup Analysis Methodology

跟进分析方法论

Overview

概述

Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.
这是一套结构化方法，可快速了解git仓库、会议纪要、sprint进度、文档修订或系统日志中的最新变更，高效解答「发生了什么变更、哪些变更最重要」的问题。

When To Use

适用场景

  • Joining ongoing work or returning after absence
  • Before planning or reviewing handoffs
  • Any "what happened and what's next" context
  • 加入正在进行的工作或缺勤后返回工作岗位
  • 规划或评审工作交接之前
  • 任何需要了解「此前发生了什么、接下来要做什么」上下文的场景

When NOT To Use

不适用场景

  • Doing detailed diff analysis - use diff-analysis instead
  • Full code review needed
    • use review-core instead
  • Doing detailed diff analysis - use diff-analysis instead
  • Full code review needed
    • use review-core instead
  • 执行详细 diff分析 - 请使用diff-analysis
  • 需要完整代码评审
    • 请使用review-core
  • 执行详细 diff分析 - 请使用diff-analysis
  • 需要完整代码评审
    • 请使用review-core

Activation

触发方式

Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"
关键词: catchup, summary, status, progress, context, handoff 提示语: "get me up to speed", "current status", "summarize progress"

Progressive Loading

渐进式加载

Load modules based on context:
Git: Load 
modules/git-catchup-patterns.md
for git commands. Consider 
sanctum:git-workspace-review
for initial data gathering.
Documents/Notes: Load 
modules/document-analysis-patterns.md
for meeting notes, sprint tracking, document revisions.
Logs/Events: Load 
modules/log-analysis-patterns.md
for time-series and metric analysis.
Always Available: 
imbue:evidence-logging
, TodoWrite workflow, structured output.
根据上下文加载对应模块：
Git: 加载
modules/git-catchup-patterns.md
获取git命令，可考虑使用
sanctum:git-workspace-review
完成初始数据收集。
文档/笔记: 加载
modules/document-analysis-patterns.md
处理会议纪要、sprint跟踪、文档修订相关内容。
日志/事件: 加载
modules/log-analysis-patterns.md
进行时间序列和指标分析。
始终可用: 
imbue:evidence-logging
, TodoWrite工作流, 结构化输出。

Required TodoWrite Items

必需的TodoWrite项

  1. catchup:context-confirmed
    - Boundaries established
  2. catchup:delta-captured
    - Changes enumerated
  3. catchup:insights-extracted
    - Themes identified
  4. catchup:followups-recorded
    - Actions captured
  1. catchup:context-confirmed
    - 已明确范围边界
  2. catchup:delta-captured
    - 已枚举所有变更
  3. catchup:insights-extracted
    - 已识别核心主题
  4. catchup:followups-recorded
    - 已记录后续行动

4-Step Methodology

四步方法论

Step 1: Confirm Context

步骤1：确认上下文

Define scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.
定义范围（git分支、sprint、会议）、基线（上一次的状态）和当前目标，可参考各模块中的命令。

Step 2: Capture Delta

步骤2：捕获变更

Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.
枚举所有变更项及相关指标，优先处理源代码/配置/文档而非生成的产物，可参考各模块中的策略。

Step 3: Extract Insights

步骤3：提炼洞察

Per item: What (change), Why (motivation), Implications (tests/risks/deps). Rollup into themes.
针对每个变更项：内容（变更是什么）、原因（变更动机）、影响（测试/风险/依赖），汇总形成核心主题。

Step 4: Record Follow-ups

步骤4：记录后续行动

Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.
记录内容包括：测试、文档、评审、阻塞问题、疑问。如果没有相关内容请明确说明。

Output Format

输出格式

undefined
undefined

Summary

Summary

[2-3 sentence theme + risk overview]
[2-3 sentence theme + risk overview]

Key Changes

Key Changes

Follow-ups

Follow-ups

  • [Action with owner]
  • [Action with owner]

Blockers/Questions

Blockers/Questions

  • [Item requiring resolution]
**Verification:** Run the command with `--help` flag to verify availability.
  • [Item requiring resolution]
**验证**: 使用`--help`参数运行命令验证其可用性。

Integration

集成

Use 
imbue:diff-analysis
for risk assessment, 
imbue:evidence-logging
for reproducibility, 
sanctum:git-workspace-review
for git data. Feed to 
brainstorming
or 
writing-plans
as needed.
使用
imbue:diff-analysis
完成风险评估，
imbue:evidence-logging
保证可复现性，
sanctum:git-workspace-review
获取git数据。可按需输入到
brainstorming
或
writing-plans
流程中。

Token Conservation

Token节省方案

Reference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.
引用路径+行号（不要复现完整内容）、汇总输出、推迟深度分析、使用渐进式加载。

Exit Criteria

退出标准

  • Four TodoWrite items completed
  • Context/delta/insights/follow-ups captured
  • Stakeholders understand state without re-reading sources
  • 完成全部四个TodoWrite项
  • 已捕获上下文/变更/洞察/后续行动
  • 利益相关者无需重读原始资料即可了解当前状态

Troubleshooting

故障排查

Common Issues

常见问题

Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior Enable verbose logging with 
--verbose
flag
找不到命令 确保已安装所有依赖且已添加到PATH中
权限错误 检查文件权限，使用合适的权限运行
异常行为 使用
--verbose
参数启用详细日志