apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Recall what a past Claude Code session did and why by locating its transcript. Use when the user asks to \"recall the session\", \"why did we do X\", or \"why was this changed\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill recall-session --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill recall-session -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill recall-session -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill recall-session -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill recall-session -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill recall-session -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill recall-session -a windsurf -y
name: recall-session description: "Recall what a past Claude Code session did and why by locating its transcript. Use when the user asks to \"recall the session\", \"why did we do X\", or \"why was this changed\"."
Locate the Claude Code transcript behind a change, a passage, or another project's session, and recover what that session did and why. Useful for answering reviewer questions, writing post-hoc explanations, or recovering forgotten context.
Accept any of:
If only a file is given, `git blame` resolves the commit that last touched the line.
Call `${CLAUDE_SKILL_DIR}/scripts/find_transcript.py` with either `--commit <sha>` or `--file <path>[:<line>]`. Pass `--cwd /path/to/repo` when searching a different repo than the current working directory.
python3 ${CLAUDE_SKILL_DIR}/scripts/find_transcript.py --file <path>:<line>
python3 ${CLAUDE_SKILL_DIR}/scripts/find_transcript.py --commit <sha>When there is no commit to resolve, because the project is not a git repository or `--file` returns `no-commit` for an uncommitted line, run `--phrase` with a distinctive stretch of the passage's current text, taken from a single line, instead. It skips git, ranks the project's transcripts by how often they handle the phrase, and returns the same JSON with `commit: null`.
python3 ${CLAUDE_SKILL_DIR}/scripts/find_transcript.py --phrase "<distinctive text from the passage>"For another project's session, run `--phrase` with `--cwd <dir>`, taking a phrase distinctive to that session, such as a command it ran or a file path it touched.
With `--commit` or `--file`, the script:
1. Resolves the commit via `git rev-parse` or `git blame` 2. Enumerates directories under the effective Claude configuration home's `projects/` tree and filters their transcripts by authoritative `cwd` records, covering path encoding, truncation, collisions, and subdirectory launches 3. Ranks candidate transcripts whose mtime is within `--window-days` of the commit (default 14) 4. Scores candidates by mentions of touched files and tool-use edits on them 5. Extracts cleaned user prompts and substantive assistant text from the top candidates
The JSON output has `status`, `commit`, `project_dir` (the top candidate's directory when matched), `project_dirs` (directories with matching `cwd` records, limited to the time window when there is a commit), and `candidates` with `session_id`, `score`, `match_reasons`, and `excerpts`.
Status values:
If `status` is `ok`:
1. Start with the top candidate (highest score). Read its excerpts first. 2. If the excerpts already answer the question, stop. If they are thin or ambiguous, read the full transcript at `jsonl_path` directly for more context. 3. Ignore candidates with low scores or scores far below the top — they are false positives. 4. When the answer spans multiple excerpts, quote the most specific one. 5. In phrase mode, the `last match at` reason marks the last time the session handled the passage. When the question is about the passage's current state, read the transcript around that point.
Synthesize a concise summary tied to the question being answered:
If `status` is anything other than `ok`, report that no transcript was found. For a change or a passage, fall back to reading the commit diff, when there is one, and the surrounding code, and say so explicitly so it's clear whether the answer still holds up. For another project's session, report the status alone.
Return the answer in this shape:
**Commit:** <short-sha> — <subject> **Transcript:** <session-id> (score <N>) <one or two paragraphs answering the question, quoting the implementer where useful>
If no transcript was found for a change or a passage:
**Commit:** <short-sha> — <subject> **Transcript:** none found (<status>) <fallback explanation derived from reading the commit and current code>
In either shape, without a commit, write the first line as `**Commit:** none (not a git repository)` or `**Commit:** none (uncommitted)`. For another project's session, write it as `**Project:** <the directory passed as --cwd>`.
Then use the TaskList tool and proceed to any remaining task.
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.