---
name: historical-memory-routing
description: Use when the user asks why something changed, what happened before, which attempts failed, or what historical context matters before modifying code in a Remix-bound repo.
---

# Historical Memory Routing

In a Remix-bound repo, treat Remix memory as the first stop for historical reasoning.

Use this skill when the user is asking about:

- why something changed
- which prompt, requirement, or discussion led to an implementation
- failed attempts, abandoned ideas, regressions, or rollbacks
- hidden assumptions, tradeoffs, or architectural reasoning
- merge request, reconcile, drift, or recovery backstory
- what historical context matters before changing a file or subsystem

Default order:

1. `remix_collab_memory_summary` for current state and recent context
2. `remix_collab_memory_search` for targeted historical lookup
3. `remix_collab_memory_timeline` when chronology matters
4. `remix_collab_memory_change_step_diff` only after identifying a relevant `changeStepId`
5. Raw git history only for exact commit, blame, ancestry, or patch details after Remix memory has narrowed the relevant change

Important rules:

- Do not start these questions with `git log`, `git show`, `git blame`, or `git diff`.
- Use bounded memory reads first, then expand to the full stored diff only when the relevant change step is known.
- If the user explicitly asks for raw git facts, raw git can be used for those exact facts, but Remix memory remains the authoritative source for intent and reasoning.
