メニュー
Use when unexpected changes appear on your branch or worktree — commits you did not make, amended or force-pushed history, or a working tree that contradicts your memory — to reconstruct who did what and decide how to proceed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Prefer tracedecay tools for codebase exploration, graph queries, and memory recall.
Use when installing a TraceDecay checkout for live local development, refreshing the globally available binary without a release, or validating agents and the daemon against unmerged TraceDecay changes.
Use when installing a TraceDecay checkout for live local development, refreshing the globally available binary without a release, or validating agents and the daemon against unmerged TraceDecay changes.
Use when listing or reading agent-managed automation skills, viewing automation run artifacts, or inspecting skills owned by the standard Hermes user install without mutating them.
Use when you need LCM, session search, transcript search, raw past-session replay, scoped/time grep, summary-DAG drill-down, branch/worktree/commit history, workflow recovery, or compaction recovery; and when driving host LCM lifecycle preflight/compress/boundary/repair.
Use before writing a new function or helper (it may already exist), and before any rename, signature, or field change — the graph lists every call site.
| name | investigating-unexpected-changes |
| description | Use when unexpected changes appear on your branch or worktree — commits you did not make, amended or force-pushed history, or a working tree that contradicts your memory — to reconstruct who did what and decide how to proceed. |
Parallel agents share branches and worktrees. Real sessions have hit this and
guessed: one Claude session found three of its branches amended under it and
called it "auto-merged... a repository watcher"; a Cursor session saw a test
file it "didn't write but which passes" and spent turns on blind git log
trying to explain it. Blind git archaeology cannot name the actor. TraceDecay
correlates every session to the branches, worktrees, and commits it touched, so
you can attribute the change instead of theorizing. Do that before you react.
Pin the objective facts first; do not act on a hunch.
git status, git log --oneline -20, and
git reflog -20 (reflog survives amends and resets — it shows HEAD moving
even when git log looks clean).tracedecay_commit_context (changed
symbols, file roles, recent commit style) to see what moved without
reading raw diffs.git diff --name-only <base>...<head> as the file boundary, then pass
those paths to tracedecay_diff_context. Treat tracedecay_branch_diff
as a summary only after its commits/files agree with that live boundary;
never act on a stale graph snapshot alone.Turn "what changed" into "who changed it" with the session-git correlation index.
tracedecay_sessions_for (git_ref: branch | worktree | commit,
value, optional since / until) lists every session correlated with the
artifact. Query the surprising commit sha first, then the branch or worktree
if the commit is unattributed.relation on each returned session:
produced — that session made the commit (the actor you are looking
for).observed — that session only saw it (a bystander, useful for timeline
but not authorship).produced hit is
trustworthy even across branch churn.Once you have the acting session id, recover why it made the change.
tracedecay_message_search (query, plus branch / commit filters, or
parent_session_id) surfaces what the actor was told to do and what it
reported — search the commit sha or the touched file names.tracedecay_lcm_grep with scope: "session" and that session_id returns
bounded raw-message snippets for the one session; scope: "all" is the
cross-session default.capped_sessions disclosure: a broad (scope: "all") grep can cap
how many sessions it scans and say so. When the acting session may have been
capped, rerun with scope: "session" and its id for complete results before
concluding.With the actor, their intent, and the delta in hand, choose:
produced session id and its goal
tell you whom to reconcile with rather than force-pushing over live work.produced commit destroys unmerged work.If a durable ownership convention emerges (for example "branch codex/* is
owned by the Codex worktree"), record it with tracedecay_fact_store so the
next session inherits it — see tracedecay:project-memory.
select:tracedecay_sessions_for,tracedecay_commit_context,tracedecay_diff_context,tracedecay_branch_diff,tracedecay_message_search,tracedecay_lcm_grep
(one batched call) — then call normally.tracedecay tool sessions_for --args '{"git_ref":"commit","value":"<sha>"}',
tracedecay tool commit_context, tracedecay tool diff_context,
tracedecay tool branch_diff,
tracedecay tool message_search, tracedecay tool lcm_grep (see
tracedecay:using-the-cli). Never query .tracedecay databases directly;
never fall back to blind git archaeology when the correlation index can name
the actor.Do not end without: the objective delta (which commits/files/symbols changed and
how HEAD moved), the attributed actor (session id + relation, or an explicit
"unattributed" when no session correlates), that session's intent from its
messages, and the chosen action (adopt / coordinate / hold). Report any
tracedecay_metrics: line.