session-review
Skill64 starsChanged 5 months agoMITView on GitHub
Generate a structured session summary for cross-session continuity. Captures key decisions, hypotheses, partial work, and knowledge references. Output is written to .Codex/session-handoff.json for the next session to load automatically.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- alexuraxin/retainertheir own version, first seen Nov 15, 2026
- amkisko/prayerstheir own version, first seen Nov 6, 2026
- reatlat/fullstory-claude-plugintheir own version, first seen Oct 30, 2026
- rhvdbergh/claude-skillstheir own version, first seen Oct 16, 2026
- matiopala/skillstheir own version, first seen Oct 15, 2026
- nirgal-soft/skillstheir own version, first seen Sep 17, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- reatlat/fullstory-claude-plugin★ 36same name
- alexuraxin/retainer★ 3same name
- amkisko/prayers★ 2same name
- matiopala/skills★ 2same name
- scottwater/skills★ 2same name
- t-nakatani/skills★ 2same name
- franckdjiongo/claude-skills★ 0same name
- nirgal-soft/skills★ 0same name
- rhvdbergh/claude-skills★ 0same name
- zl3311/alpha-mining★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository102 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumptionsSkill
- capture-learningSkill
- Codex-opus-4-6-promptingSkill
- Codex-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- diagramSkill
- distillSkill
- effect-tsSkill
- escalateSkill
- evalSkill
- experimentSkill
- hddSkill
- hub-auditSkill
- hub-collabSkill
- implementSkill
- knowledgeSkill
- peer-notebook-delivery-guardSkill
- research-taskSkill
- source-command-hdd-decideSkill
- source-command-hdd-hddSkill
- source-command-hdd-researchSkill
- source-command-hdd-stage-adrSkill
- source-command-hdd-validateSkill
- statusSkill
- supabaseSkill
- synthesizeSkill
- tasteSkill
- teamSkill
- test-suiteSkill
- theseus-protocolSkill
- thoughtbox:debugSkill
- thoughtbox:decisionSkill
- thoughtbox:evolutionSkill
- thoughtbox:knowledge-querySkill
- thoughtbox:onboardSkill
- thoughtbox:refactorSkill
- thoughtbox:researchSkill
- thoughtbox:session-reviewSkill
- thoughtbox-teamSkill
- ulc-loopSkill
- ulysses-protocolSkill
- workflow-brainstormingSkill
- workflow-ideationSkill
- workflow-reflectionSkill
- workflow-revisionSkill
- workflows-compoundSkill
- workflowSkill
- workflows-planSkill
- workflows-reviewSkill
- workflows-workSkill
- workflow-tournamentSkill
- assumptionsSkill
- capture-learningSkill
- claude-opus-4-6-promptingSkill
- claude-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Run git log --oneline -20 to see recent commits this session
- Distinctive: line 29
Run git status to see uncommitted work
- Distinctive: line 30
Run git diff --stat to see scope of changes
- Very specific: line 31
Check .Codex/state/memory-calibration.json for pattern detection state
- Distinctive: line 32
Read MEMORY.md for any updates made this session
- Very specific: line 47
Write the session summary to .Codex/session-handoff.json (single file, overwritten each time) using this schema:
- Distinctive: line 108
Verify the handoff file was written successfully
- Distinctive: line 110
If there are uncommitted changes, warn about them
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate a structured session summary for cross-session continuity.
Context
$ARGUMENTS
Loop Building Blocks
| Loop | Purpose | Reference |
| Consistency Check | Validate session summary against evidence | @loops/refinement/consistency-check.md |
| Documentation | Generate structured session review | @loops/authoring/documentation.md |
See @loops/README.md for the full loop library.
Workflow
Phase 1: Gather Session State (Observe)
- Run
git log --oneline -20to see recent commits this session - Run
git statusto see uncommitted work - Run
git diff --statto see scope of changes - Check
.Codex/state/memory-calibration.jsonfor pattern detection state - Read MEMORY.md for any updates made this session
Phase 2: Synthesize Session Context (Orient)
From the gathered data, identify:
- Key Decisions: What architectural or design choices were made and why
- Open Hypotheses: What questions remain unanswered, what investigations are pending
- Partial Work: What was started but not finished, with enough context to resume
- Knowledge Discovered: New patterns, gotchas, or insights worth preserving
- Blocked Items: What's blocked and on what
- Next Steps: What the next session should prioritize
Phase 3: Write Session Handoff (Act)
Write the session summary to .Codex/session-handoff.json (single file, overwritten each time) using this schema:
{
"version": "1.0.0",
"session_id": "<from git>",
"timestamp": "<ISO 8601>",
"branch": "<current git branch>",
"duration_estimate": "<approximate session duration>",
"summary": "<1-2 sentence summary of what happened>",
"key_decisions": [
{
"decision": "<what was decided>",
"reasoning": "<why>",
"alternatives_considered": ["<alt1>", "<alt2>"],
"files_affected": ["<file1>", "<file2>"]
}
],
"hypotheses": [
{
"hypothesis": "<what's being investigated>",
"evidence_for": ["<supporting evidence>"],
"evidence_against": ["<counter evidence>"],
"next_test": "<what to try next>"
}
],
"partial_work": [
{
"description": "<what was started>",
"status": "<how far along>",
"resume_from": "<specific file:line or commit to resume from>"
}
],
"knowledge_references": [
{
"store": "<MEMORY.md | Thoughtbox | git>",
"reference": "<specific entity/issue/commit>",
"relevance": "<why the next session needs this>"
}
],
"blocked_items": [
{
"item": "<what's blocked>",
"blocker": "<what's blocking it>",
"workaround": "<if any>"
}
],
"failed_approaches": [
{
"what": "<what was tried>",
"why": "<why it failed>",
"lesson": "<what to do instead>"
}
],
"next_priorities": ["<priority 1>", "<priority 2>", "<priority 3>"],
"warnings": ["<things the next session should watch out for>"]
}Phase 4: Verify and Report (Decide)
- Verify the handoff file was written successfully
- Print a human-readable summary to the console
- If there are uncommitted changes, warn about them
Output
Present a concise summary:
## Session Handoff Written
File: .Codex/session-handoff.json
Branch: {branch}
Commits this session: {N}
Open hypotheses: {N}
Partial work items: {N}
### Top 3 Priorities for Next Session
1. {priority}
2. {priority}
3. {priority}
### Warnings
- {warning}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

