Consult is automatic at the start of implement.execute, implement.verify, and review.code (see "When to Consult" below).

1. Capture: Record a Learning

When to Capture

When NOT to Capture

• Generic best practices already covered by coding-guidelines.md or .instructions.md
• One-time errors caused by typos, environment issues, or transient failures
• Learnings about the framework itself (report as issues instead)
• Context that only applies to a single task and will not recur
• Observations with no actionable guidance ("this was hard" is not a learning)

Capture Procedure

1. Read .memory/harness-learnings.md (create from template if it does not exist)
2. Deduplicate: scan existing entries for overlap
   • Match criteria: overlapping Scope (shared file paths or modules) AND similar failure type
   • If match found: increment Occurrences, update Last seen, upgrade Confidence if warranted
   • If no match: append new entry with next sequential L-NNN ID
3. Assign fields for new entries:
   • Phase: the lifecycle phase where this learning is most relevant for consumption (not necessarily where it was captured). A review finding about missing error handling should have Phase = implement if the fix belongs at coding time.
   • Dimension: what it regulates (maintainability, architecture, behaviour)
   • Scope: concrete file paths, directories, or module names. Use glob patterns when appropriate (e.g., src/api/**, *.controller.ts). This is the primary field agents use to match learnings to their current task.
   • Pattern: factual description of what happened (the observation)
   • Guidance: actionable instruction for what to do differently (the prescription). Must include file paths, commands, or specific checks.

…

git-branch

帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。

review

用于代码与分支审查，综合检查正确性、兼容性、架构、测试、性能与安全问题。