phase-10b-durable-timeline-re-reviewer — Claude Code prompt
The phase-10b-durable-timeline-re-reviewer prompt for Claude Code re-audits fixes in Phantom PR #106 Phase 10B, checking durable timelines for secret leaks and validating session resume states.
Apache-2.0 ★ 1,497 updated 2026-06-16
.claude/commands/phase-10b-durable-timeline-re-reviewer.mdWhat phase-10b-durable-timeline-re-reviewer does
This prompt configures Claude Code as a principal reviewer inspecting the local branch at /Users/truffle/work/phantom-pr-106-push. The instructions strictly forbid modifying or reverting files. The review validates fixes for three prior defects: secret leakage in persistent summaries, premature restart recovery on post-terminal events, and stale migration assertions.
The analysis focuses on src/chat/run-timeline.ts, event logging, database schema tests, and chat UI store hooks. The required output begins with Verdict: PASS or itemizes actionable findings by severity from P0 to P2, backed by specific file and line numbers rather than speculative summaries.
Because repository-wide bunx biome check . contains pre-existing lint diagnostics outside Phase 10B, the prompt explicitly instructs the reviewer to ignore diagnostics outside changed files.
What it helps with
- audit durable chat timelines for credential leaks and raw tool output
- verify session resume logic against post-terminal suggestion events
- test replay event idempotency to prevent duplicate messages upon reconnect
- inspect migration test coverage, indexes, and cascade delete behavior
Example prompts for the agent
- /phase-10b-durable-timeline-re-reviewer
- Review the Phase 10B branch using
.claude/commands/phase-10b-durable-timeline-re-reviewer.md
How to install phase-10b-durable-timeline-re-reviewer
Manually: put the files in place
.claude/commands/phase-10b-durable-timeline-re-reviewer.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phase-10b-durable-timeline-re-reviewer
How to install phase-10b-durable-timeline-re-reviewer in Claude Code?
Place the prompt file at .claude/commands/phase-10b-durable-timeline-re-reviewer.md in your project root.
What does phase-10b-durable-timeline-re-reviewer do?
It reviews code changes in Phantom PR #106 Phase 10B, verifying credential safety, event replay idempotency, and database migrations without modifying any files.
Does this prompt run linters across the entire repository?
No, it focuses strictly on Phase 10B changes, deliberately ignoring unrelated repository lint errors reported by Biome.
Source text
phase-10b-durable-timeline-re-reviewer.md · Apache-2.0
ultrathink. ultrathink. ultrathink. You are a principal engineer, principal architect, and principal product manager at Anthropic reviewing Phantom PR #106 Phase 10B after fixes. You are not alone in the codebase. Do not edit files. Do not revert anything. Your job is to verify the current branch in `/Users/truffle/work/phantom-pr-106-push` and report only actionable findings. Context: - Phantom PR #106 is `codex/murph-agent-runtime-clean`. - Phase 10B adds durable Murph chat run timelines and route-load replay state. - The prior review found three issues: 1. P1: durable timeline summaries could persist raw secrets or raw tool output. 2. P2: resume state treated benign post-terminal `session.suggestion` frames as incomplete tails. 3. P2: migration tests were stale and did not assert the new table/indexes. - These fixes are now implemented in the current worktree. Files to inspect first: - `src/chat/run-timeline.ts` - `src/chat/__tests__/run-timeline.test.ts` - `src/chat/event-log.ts` - `src/chat/sse.ts` - `src/chat/http-handlers.ts` - `src/chat/__tests__/event-log.test.ts` - `src/chat/__tests__/http-resume.test.ts` - `src/db/schema.ts` - `src/db/__tests__/migrate.test.ts` - `chat-ui/src/lib/chat-store.ts` - `chat-ui/src/hooks/use-chat.ts` - `chat-ui/src/components/message-list.tsx` Review questions: 1. Does the durable timeline persist any raw tool stdout/stderr, raw command arguments, raw OAuth query params, AWS-style access keys, private keys, bearer tokens, cookies, or other credential-shaped values? 2. Does resume recovery now avoid synthetic server-restart recovery for a completed run followed only by benign post-terminal suggestion events? 3. Does resume recovery still emit recovery for genuinely incomplete tails? 4. Are replay events idempotent enough to avoid duplicate assistant/user messages and duplicate final text after route load or reconnect? 5. Are the migration count, migration indices, table shape, indexes, and cascade/delete behavior covered well enough for this phase? 6. Is there any P0/P1/P2 issue in the current implementation that should block committing and pushing this phase? Verification commands already run by the orchestrator: - `bun test` - `cd chat-ui && bun test` - `bun run typecheck` - `cd chat-ui && bun run typecheck` - targeted `bunx biome check` on all files changed by Phase 10B - `git diff --check` Full repo `bunx biome check .` is not currently a clean gate because the repository has unrelated pre-existing formatting and lint diagnostics outside the changed set. Do not report that as a Phase 10B finding unless a diagnostic is in files changed by this phase and is newly relevant. Output format: - Start with `Verdict: PASS` if there are no P0/P1/P2 findings. - If there are findings, list them first by severity with file and line references. - Then include test gaps or residual risks. - Keep it concise and evidence-based. Agent summaries are not evidence; read the files.
© ghostwright · Apache-2.0 · ghostwright/phantom