rule-of-two-detector
Analyze git history to detect Rule of Two violations - patterns that have happened twice and should be documented before the third occurrence. Use when the user asks to find documentation gaps, run a git learning analysis, or detect repeated patterns in the codebase. Also activates as part of /maintain-context-tree.
drift-detector
Validate Context Tree documentation claims against actual code, detect drift, and prune stale or incorrect content. Use when the user asks to audit documentation quality, check whether docs are still accurate, or validate architectural claims. Also activates as part of /maintain-context-tree.
learning-capture
Capture undocumented learnings into the Context Tree - either by reviewing recent git commits (Learning Review mode) or by offering proactive capture during normal work when a non-obvious synthesis is produced. Use when reviewing recent development for missed insights, or naturally during a session when a debugging discovery, architectural realization, or non-obvious cross-file synthesis happens. Also activates as part of /maintain-context-tree.
memory-promoter
Scan Claude Code's auto-memory directory (~/.claude/projects/<proj>/memory/) for entries that should be promoted into the committed Context Tree. Read-only of memory; verifies each candidate against code; offers to file into the appropriate Context Tree doc with user approval. Use when reviewing what auto-memory has accumulated, or as part of /maintain-context-tree.
tree-health
Quick structural health check on a Context Tree - validate links, file sizes, frontmatter presence, knowledge.yaml routing entries, and overall tree shape. Use when the user asks for a quick context tree health check, or before/after restructuring. Also activates as part of /maintain-context-tree.