phase-10i-transcript-recovery-re-review — Claude Code prompt
The phase-10i-transcript-recovery-re-review prompt guides Claude Code through a second review of transcript-recovery fixes, including project file inspection, required checks, and a written report.
Apache-2.0 ★ 1,497 updated 2026-06-16
.claude/commands/phase-10i-transcript-recovery-re-review.mdWhat phase-10i-transcript-recovery-re-review does
The prompt asks Claude Code to reassess transcript-recovery changes for Phantom-on-Murph. It directs the agent to revisit earlier P2 findings and look for new P0–P2 regressions, including session-scoped search, redaction of sensitive values, and handling of attachments. The report should list findings by severity and include verification results.
Claude Code is instructed to read the named project guidance and source files, inspect the changes, then run the specified tests, bun run lint, and bun run typecheck. It must save the report as phase-10i-transcript-recovery-re-review.md and leave production code and commits untouched. The paths and checks assume the referenced project layout, so the prompt depends on access to that repository and its files.
What it helps with
- recheck whether earlier P2 findings are resolved
- look for new P0–P2 regressions in the changes
- verify search stays within the bound Phantom web chat session
- review redaction of credentials and treatment of attachments
- record test, lint, and typecheck results in a report
Example prompts for the agent
- Re-review the transcript recovery fixes and save your findings in
phase-10i-transcript-recovery-re-review.md. - Inspect the listed files, run the required tests,
bun run lint, andbun run typecheck; do not edit production code. - Check how secrets and attachments are handled, then include verification results in the severity-ordered report.
How to install phase-10i-transcript-recovery-re-review
Manually: put the files in place
.claude/commands/phase-10i-transcript-recovery-re-review.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about phase-10i-transcript-recovery-re-review
How do I install phase-10i-transcript-recovery-re-review in Claude Code?
Place the command file at .claude/commands/phase-10i-transcript-recovery-re-review.md. Then invoke phase-10i-transcript-recovery-re-review in Claude Code.
What does phase-10i-transcript-recovery-re-review do?
It instructs Claude Code to revisit transcript-recovery fixes, inspect specified project files, assess earlier findings and possible regressions, run checks, and write a report.
Which checks does this prompt require?
Run the specified test suite with bun test, followed by bun run lint and bun run typecheck. Include each command and its result in the report.
Source text
phase-10i-transcript-recovery-re-review.md · Apache-2.0
ultrathink. ultrathink. ultrathink. You are a principal engineer, principal architect, and principal product manager at Anthropic, all three at once. You are independently re-reviewing the Phase 10I Phantom-on-Murph transcript recovery fixes after a prior reviewer found two P2 issues. No context anxiety. No token limits. No time pressure. No cost anxiety. No "v2" thinking. There is no v2. Build it right. Take as long as you need. ## Mission Review the latest worktree and decide whether the previous P2 findings are resolved without introducing new P0, P1, or P2 regressions. ## Required Reading Read these files from disk, not summaries: 1. `/Users/truffle/.claude/AGENTS.md` 2. `/Users/truffle/.claude/CLAUDE.md` 3. `/Users/truffle/work/murph/QUALITY-BAR.md` 4. `/Users/truffle/work/phantom-murph-hardening/CLAUDE.md` 5. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-transcript-recovery-review.md` 6. `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-transcript-recovery-implementation.md` Then inspect the changed source and tests: 1. `src/agent/mcp-server-factory.ts` 2. `src/agent/runtime.ts` 3. `src/agent/chat-query.ts` 4. `src/agent/in-process-reflective-tools.ts` 5. `src/chat/continuity-context.ts` 6. `src/chat/transcript-search.ts` 7. `src/chat/redaction.ts` 8. `src/chat/run-timeline.ts` 9. `src/chat/__tests__/transcript-search.test.ts` 10. `src/agent/__tests__/reflective-transcript-tools.test.ts` 11. `src/chat/__tests__/continuity-context.test.ts` ## Questions To Answer 1. Is the soft-delete lifecycle fixed against the real `ChatSessionStore.softDelete` path? 2. Is transcript search restricted to the current bound Phantom web chat session? 3. Does the new MCP factory context preserve existing non-chat MCP factories and main runtime paths? 4. Is transcript output sufficiently redacted for credential-shaped values, private keys, AWS keys, magic links, cookies, and base64 payloads? 5. Does structured extraction avoid dumping unknown raw objects or attachment payloads? 6. Did the shared redaction helper preserve durable run timeline behavior? 7. Are the tests adequate for this slice? ## Required Verification Run at minimum: ```bash bun test src/chat/__tests__/transcript-search.test.ts src/chat/__tests__/continuity-context.test.ts src/agent/__tests__/reflective-transcript-tools.test.ts src/chat/__tests__/run-timeline.test.ts src/agent/__tests__/agent-sdk-boundary-callers.test.ts src/agent/__tests__/murph-context.test.ts bun run lint bun run typecheck ``` You may run additional commands if needed. ## Output Contract Write the report to: `/Users/truffle/work/phantom-murph-hardening/research/chat-experience/phase-10i-transcript-recovery-re-review.md` Lead with findings, ordered by severity. If there are no P0, P1, or P2 findings, say that explicitly. Include commands run and their results. Do not edit production code. Do not commit. ultrathink before finalizing. Treat agent summaries as non-evidence; read the actual files and command output.
© ghostwright · Apache-2.0 · ghostwright/phantom