Back to Details

groove-utilities-memory-mistakes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

groove-utilities-memory-mistakes

groove-utilities-memory-mistakes

Use $ARGUMENTS as the mistake description if provided (e.g. 
--list
to show open incidents only).
如果提供了$ARGUMENTS则将其作为错误描述使用（例如使用
--list
仅展示未解决的事件）。

Outcome

执行结果

The workflow mistake is logged, its root cause is fixed in the relevant memory or learned file, and the lesson is graduated to 
<memory>/learned/<topic>.md
. The incident is closed.
工作流错误会被记录，其根本原因会在相关记忆或已学习文件中得到修复，经验教训会被归档到
<memory>/learned/<topic>.md
中，事件将被关闭。

Acceptance Criteria

验收标准

  • Incident is recorded with root cause and fix
  • Permanent fix applied to 
    .groove/memory/learned/<topic>.md
  • Incident marked resolved
  • 事件会记录根本原因和修复方案
  • 永久修复会被应用到
    .groove/memory/learned/<topic>.md
  • 事件标记为已解决

Task backend

任务后端

Read 
tasks:
from 
.groove/index.md
. Incidents are tracked as tasks in the configured backend. If no task backend is configured (
tasks: none
), tell the user to run 
/groove-utilities-task-install
first.
Incidents are stored as bugs under a shared "Groove Memory" milestone → "Mistakes" epic.
读取
.groove/index.md
中的
tasks:
配置。事件会作为任务在配置的后端中进行跟踪。如果未配置任务后端（
tasks: none
），请告知用户先运行
/groove-utilities-task-install
。
事件作为bug存储在共享的"Groove Memory"里程碑下的"Mistakes"史诗中。

Ensure parent hierarchy

确保父层级存在

Before any operation, resolve or create the parent epic:
  1. Find or create the Groove Memory milestone: 
    • beans list -t milestone --search "Groove Memory" -q
      — if non-empty, use first ID; otherwise 
      beans create "Groove Memory" -t milestone
  2. Find or create the Mistakes epic under that milestone: 
    • beans list -t epic --parent <milestone-id> --search "Mistakes" -q
      — if non-empty, use first ID; otherwise 
      beans create "Mistakes" -t epic --parent <milestone-id>
在执行任何操作前，解析或创建父史诗：
  1. 查找或创建Groove Memory里程碑： 
    • beans list -t milestone --search "Groove Memory" -q
      — 如果返回非空，使用第一个ID；否则执行
      beans create "Groove Memory" -t milestone
  2. 查找或创建该里程碑下的Mistakes史诗： 
    • beans list -t epic --parent <milestone-id> --search "Mistakes" -q
      — 如果返回非空，使用第一个ID；否则执行
      beans create "Mistakes" -t epic --parent <milestone-id>

--list

--list

  1. Resolve 
    <parent-id>
  2. beans list --parent <parent-id> -t bug -s in-progress
  3. Display as numbered list: 
    1. [<id>] <title>
  4. If empty: print "No open incidents."
  1. 解析得到
    <parent-id>
  2. beans list --parent <parent-id> -t bug -s in-progress
  3. 以编号列表形式展示：
    1. [<id>] <title>
  4. 如果结果为空：打印"无未解决事件。"

Log and resolve an incident

记录并解决事件

  1. Resolve 
    <parent-id>
  2. Get description from $ARGUMENTS or ask: "What mistake did I make?"
  3. Ask: "Root cause — why did it happen?" (propose from context; user confirms)
  4. Ask: "What fix should be applied?" (propose; user confirms)
  5. beans create "<description>" -t bug --parent <parent-id> -s in-progress
  6. Apply the fix immediately (edit the relevant file)
  7. Ask: "Which learned topic? (e.g. 
    anti-patterns
    , 
    tools
    )" — suggest based on root cause
  8. Append lesson to 
    <memory>/learned/<topic>.md
    under 
    ## YYYY-MM-DD
    heading
  9. beans update <id> -s completed
  10. Report: "Incident resolved → learned/<topic>.md"
  1. 解析得到
    <parent-id>
  2. 从$ARGUMENTS获取描述，或者询问用户："我犯了什么错误？"
  3. 询问用户："根本原因是什么？为什么会发生？"（从上下文给出建议，由用户确认）
  4. 询问用户："应该应用什么修复方案？"（给出建议，由用户确认）
  5. beans create "<description>" -t bug --parent <parent-id> -s in-progress
  6. 立即应用修复（编辑相关文件）
  7. 询问用户："属于哪个学习主题？（例如
    anti-patterns
    、
    tools
    ）" — 根据根本原因给出建议
  8. 将经验教训追加到
    <memory>/learned/<topic>.md
    的
    ## YYYY-MM-DD
    标题下
  9. beans update <id> -s completed
  10. 报告："事件已解决 → learned/<topic>.md"

Constraints

约束条件

  • Read 
    tasks:
    and 
    memory:
    from 
    .groove/index.md
  • Requires a configured task backend — if 
    tasks: none
    , prompt user to install one
  • Never auto-create incidents without user confirmation
  • Root cause is required before resolving — do not skip the audit step
  • Parent hierarchy is idempotent — always check before creating
  • If the fix targets a 
    skills/
    file: note that 
    skills/
    is managed by groove:update; redirect fix to 
    learned/anti-patterns.md
  • 从
    .groove/index.md
    读取
    tasks:
    和
    memory:
    配置
  • 需要已配置的任务后端 — 如果
    tasks: none
    ，提示用户先安装
  • 未经用户确认绝不自动创建事件
  • 解决前必须明确根本原因 — 不得跳过审计步骤
  • 父层级操作是幂等的 — 创建前始终先检查
  • 如果修复针对的是
    skills/
    目录下的文件：请注意
    skills/
    由groove:update管理，请将修复内容重定向到
    learned/anti-patterns.md