Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Recall why a past change was made by locating the Claude Code transcript that produced it.
Install Recall Rationale
$ npx skills add tobihagemann/turbo --skill recall-rationale -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo recall-rationale --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/recall-rationale .claude/skills/recall-rationale && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .claude/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationaleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tobihagemann/turbo --skill recall-rationale -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo recall-rationale --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/recall-rationale .agents/skills/recall-rationale && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .agents/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill recall-rationale -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo recall-rationale --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/recall-rationale .cursor/skills/recall-rationale && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .cursor/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tobihagemann/turbo.git --path claude/skills/recall-rationale--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tobihagemann/turbo --skill recall-rationale -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo recall-rationale --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/recall-rationale .gemini/skills/recall-rationale && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .gemini/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tobihagemann/turbo recall-rationaleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tobihagemann/turbo --skill recall-rationale -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/recall-rationale .github/skills/recall-rationale && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .github/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill recall-rationale -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo recall-rationale --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/recall-rationale .opencode/skills/recall-rationale && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "recall-rationale" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/recall-rationale into .opencode/skills/recall-rationale/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recall-rationale", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
recall-rationale- GitHub stars
- 408
- Token cost
- ~1.3k tokens
- SKILL.md length
- 673 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Recall why a past change was made by locating the Claude Code transcript that produced it.
- Works in 3 steps: Resolve the Commit and Run the Script → Read and Synthesize → Output
- The user asks to recall the rationale
- SKILL.md covers Inputs, Step 1: Resolve the Commit and…, Step 2: Read and Synthesize and Step 3: Output, plus 1 more section
- Runs Python scripts from its folder; calls python3 and git
What it does
Recall Rationale is an agent skill from tobihagemann/turbo. Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/find_transcript.py`).
It sits in Development. It works with Git. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- The user asks to recall the rationale
- Find the rationale
- Look up the rationale
- Why did we do X
Example prompts
- “recall the rationale”
- “find the rationale”
- “look up the rationale”
- “/recall-rationale”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Recall Rationale loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 673 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 673 words, ~1,331 tokens.
Download SKILL.mdSave it as
.claude/skills/recall-rationale/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- recall-rationale
- description
- Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
Recall Rationale
Locate the Claude Code transcript that produced a given change and recover why it was made. Useful for answering reviewer questions, writing post-hoc explanations, or recovering forgotten context.
Inputs
Accept any of:
- A commit SHA
- A file path, optionally with a line number (
<path>:<line>) - A reviewer question plus surrounding context (file and line)
- A passage with no commit behind it, because the project is not a git repository or the change is uncommitted
If only a file is given, git blame resolves the commit that last touched the line.
Step 1: Resolve the Commit and Run the Script
Call 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 <skill-dir>/scripts/find_transcript.py --file <path>:<line>
python3 <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 <skill-dir>/scripts/find_transcript.py --phrase "<distinctive text from the passage>"With --commit or --file, the script:
- Resolves the commit via
git rev-parseorgit blame - Enumerates directories under the effective Claude configuration home's
projects/tree and filters their transcripts by authoritativecwdrecords, covering path encoding, truncation, collisions, and subdirectory launches - Ranks candidate transcripts whose mtime is within
--window-daysof the commit (default 14) - Scores candidates by mentions of touched files and tool-use edits on them
- 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:
ok— candidates returnedno-commit— couldn't resolve a commitno-transcripts— the effective Claude configuration home has no project transcript directoriesno-match— transcripts exist but none match the touched files in the window, or none mention the phrase
Show full SKILL.md (331 more words)Show less
Step 2: Read and Synthesize
If status is ok:
- Start with the top candidate (highest score). Read its excerpts first.
- If the excerpts already explain the change, stop. If they are thin or ambiguous, read the full transcript at
jsonl_pathdirectly for more context. - Ignore candidates with low scores or scores far below the top — they are false positives.
- When the rationale spans multiple excerpts, quote the most specific one.
- In phrase mode, the
last match atreason 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:
- Lead with the why. The diff already shows the what.
- Quote the implementer's own words when they already say it well.
- Keep it to one or two paragraphs. Don't narrate the whole session.
If status is anything other than ok, report that no rationale was found and fall back to reading the commit diff, when there is one, and the surrounding code. Say so explicitly so it's clear whether the answer still holds up.
Step 3: Output
Return the rationale in this shape:
**Commit:** <short-sha> — <subject>
**Transcript:** <session-id> (score <N>)
<one or two paragraphs of rationale, quoting the implementer where useful>If no transcript was found:
**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).
Then use the TaskList tool and proceed to any remaining task.
Rules
- Treat excerpts as evidence, not ground truth. The implementer's intent at the time may have changed. If the current code contradicts an excerpt, note the discrepancy.
- Only read the full
.jsonlif the excerpts are insufficient. These files are large. - Never quote noise prefixes like
<command-message>or skill-loading stubs. The script filters these out, but stay alert if reading a transcript directly. - If multiple candidates have similar high scores, name both and prefer the one whose time window contains the commit, or, without a commit, the one whose tool calls carry the phrase.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in claude/skills/recall-rationale of tobihagemann/turbo.
- SKILL.md
- scripts/find_transcript.py
Open the folder on GitHubat commit 931eda5
Compare with similar skills
Recall Rationale next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Recall Rationale this skilltobihagemann/turbo | 408 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 35 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Assess Technical Debt
tobihagemann/turbo
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.
Codex Exec
tobihagemann/turbo
Run autonomous task execution using the codex CLI. An agent skill from tobihagemann/turbo.
Related
Works with
Categories
Questions about Recall Rationale
What does Recall Rationale do?
Recall why a past change was made by locating the Claude Code transcript that produced it. Recall Rationale is an agent skill from tobihagemann/turbo. Recall why a past change was made by locating the Claude Code transcript that produced it.
When should I use Recall Rationale?
Recall Rationale fits situations like: the user asks to recall the rationale; find the rationale; look up the rationale; why did we do X.
How do I install Recall Rationale in Claude Code?
Run `npx skills add tobihagemann/turbo --skill recall-rationale -a claude-code`. Or copy the skill folder (claude/skills/recall-rationale in tobihagemann/turbo) into .claude/skills/recall-rationale in your project. Claude Code loads it when a task matches its description.
How do I install Recall Rationale in Codex?
Run `npx skills add tobihagemann/turbo --skill recall-rationale -a codex`. Or copy the skill folder (claude/skills/recall-rationale in tobihagemann/turbo) into .agents/skills/recall-rationale in your project. Codex loads it when a task matches its description.
Can I use Recall Rationale in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill recall-rationale -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/recall-rationale, .gemini/skills/recall-rationale, .github/skills/recall-rationale and .opencode/skills/recall-rationale in your project.
What does Recall Rationale need to run?
Going by SKILL.md and its folder, Recall Rationale needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.
Does Recall Rationale access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Recall Rationale safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Recall Rationale use?
Recall Rationale is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Recall Rationale use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Recall Rationale?
Skills that share tags, products or a category with Recall Rationale: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Finishing A Development Branch (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Recall Rationale?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.