tobihagemann/recall-reasoning
codex/skills/recall-reasoning/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo recall-reasoningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 4:57 AM137.8s1 file scanned
SKILL.md
- name:
- recall-reasoning
- description:
- 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\".
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:
git rev-parse <sha>
git blame -L <line>,<line> -- <path>
Collect the commit subject, changed files, and relevant diff:
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:
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 with the why. The diff already shows the what.
- Quote or paraphrase only the relevant reasoning.
- Keep the explanation to one or two paragraphs.
If no session reasoning was found:
- Read the commit diff and surrounding current code.
- Infer the most likely rationale from the code, tests, plan/spec artifacts, and PR context.
- Mark the output as fallback-derived.
Step 4: Output
When session reasoning was found:
**Commit:** <short-sha> — <subject>
**Session:** <session reference>
<one or two paragraphs of reasoning>
When no session reasoning was found:
**Commit:** <short-sha> — <subject>
**Session:** none found
<fallback explanation derived from git history and current code>
Then update or check the active plan and proceed to any remaining task.
Rules
- Treat session excerpts as evidence, not ground truth.
- Do not read full transcript files unless excerpts are insufficient.
- If current code contradicts a remembered rationale, note the discrepancy.
Related Skills
tobihagemann/codex-exec
tools
VerifiedTrustedCommunity
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
334SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026