recall-reasoning
Recall the reasoning behind a past change from Codex session history when available, falling back to commit diff and surrounding code. Use when the user asks to \"recall reasoning\", \"find reasoning\", \"look up reasoning\", \"recall implementation reasoning\", \"find the rationale\", \"why did I do X\", \"recall from transcripts\", or \"find the transcript for this commit\".
Profile →npx skills add majiayu000/claude-skill-registry --skill recall-reasoning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Recall Reasoning Recover the reasoning behind a change. Prefer Codex session history when it can be found; otherwise derive the explanation from git history and current code. ## Inputs Accept any of: - A commit SHA - A file path, optionally with a line number (`<path>:<line>`) - A reviewer question plus surrounding context If only a file is given, use `git blame` to resolve the commit that last touched the line. ## Step 1: Resolve the Commit Resolve the target commit: ```bash git rev-parse <sha> git blame -L <line>,<line> -- <path> ``` Collect the commit subject, changed files, and relevant diff: ```bash git show --stat --oneline <sha> git show -- <path> ``` ## Step 2: Search Codex Session History If Codex session files are available, search them for the commit SHA, touched file paths, branch name, and distinctive user request text: ```bash rg "<sha>|<file>|<branch>|<distinctive text>" ~/.codex/sessions ``` Read only the smallest relevant transcript excerpts. Prefer sessions close to the commit time and sessions that mention both the file and the task. If no matching session is found, continue with the fallback path. ## Step 3: Synthesize If session reasoning was found: - Lead wi
- Inputs
- Step 1: Resolve the Commit
- Step 2: Search Codex Session History
- Step 3: Synthesize
- Step 4: Output
- Rules
git rev-parse <sha> git blame -L <line>,<line> -- <path> git show --stat --oneline <sha> git show -- <path> rg "<sha>|<file>|<branch>|<distinctive text>" ~/.codex/sessions
What does the recall-reasoning skill do?
Recall the reasoning behind a past change from Codex session history when available, falling back to commit diff and surrounding code. Use when the user asks to \"recall reasoning\", \"find reasoning\", \"look up reasoning\", \"recall implementation reasoning\", \"find the rationale\", \"why did I do X\", \"recall from transcripts\", or \"find the transcript for this commit\".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill recall-reasoning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.