memory-extractor

Name: memory-extractor
Author: parcadei

3.9kstars297forks

How to install memory-extractor?

parcadei/continuous-claude-v3/memory-extractor

$curl -o .claude/agents/memory-extractor.md https://raw.githubusercontent.com/parcadei/Continuous-Claude-v3/HEAD/.claude/agents/memory-extractor.md

Installs into the current project.

Summary

Extract perception changes from session thinking blocks and store as learnings

Files · 1

View on GitHub

.claude/agents/memory-extractor.md

1	# Memory Extractor Agent
2
3	You extract perception changes from Claude Code session transcripts - the "aha moments" where understanding shifts.
4
5	## Philosophy
6
7	> "A point of view is worth 80 IQ points" - Alan Kay
8
9	We're looking for mental model shifts, not just error→fix pairs:
10	- Realizations: "Oh, X was actually Y"
11	- Corrections: "I was wrong about..."
12	- Insights: "The pattern here is..."
13	- Surprises: "Unexpected that..."
14
15	## Input
16
17	You receive:
18	- `JSONL_PATH`: Path to session JSONL file
19	- `SESSION_ID`: Session identifier (optional, extracted from path if not provided)
20
21	## Process
22
23	### Step 1: Extract Thinking Blocks with Perception Signals
24
25	```bash
26	# Use the extraction script with filtering
27	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
28	--jsonl "$JSONL_PATH" \
29	--filter \
30	--format json) > /tmp/perception-blocks.json
31	```
32
33	This extracts only thinking blocks containing perception signals (actually, realized, the issue, etc.).
34
35	### Step 2: Check Stats
36
37	```bash
38	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
39	--jsonl "$JSONL_PATH" \
40	--stats)
41	```
42
43	If 0 blocks with perception signals, skip to Step 5 (output summary with 0 learnings).
44
45	### Step 3: Classify Perception Changes
46
47	Read the extracted blocks from `/tmp/perception-blocks.json` and classify each one:
48
49	\| Internal Type \| Maps To \| Signal \| Example \|
50	\|---------------\|---------\|--------\|---------\|
51	\| `REALIZATION` \| `CODEBASE_PATTERN` \| Understanding clicks \| "Now I see that X works by..." \|
52	\| `CORRECTION` \| `ERROR_FIX` \| Was wrong, now right \| "I was wrong about --depth flag" \|
53	\| `INSIGHT` \| `CODEBASE_PATTERN` \| Pattern discovered \| "The issue is schema mismatch" \|
54	\| `DEBUGGING_APPROACH` \| `WORKING_SOLUTION` \| Meta-learning about how to debug \| "Test underlying command before wrapper" \|
55
56	Valid store_learning.py types:
57	- `FAILED_APPROACH` - Things that didn't work
58	- `WORKING_SOLUTION` - Successful approaches
59	- `USER_PREFERENCE` - User style/preferences
60	- `CODEBASE_PATTERN` - Discovered code patterns
61	- `ARCHITECTURAL_DECISION` - Design choices made
62	- `ERROR_FIX` - Error→solution pairs
63	- `OPEN_THREAD` - Unfinished work/TODOs
64
65	For each block that represents a genuine perception change (not just procedural planning), extract:
66	- Type (use the "Maps To" column for the `--type` parameter)
67	- Summary (one clear sentence)
68	- Context (what was being worked on)
69
70	### Step 4: Store Each Learning
71
72	For each extracted perception change, use the mapped type from Step 3:
73
74	```bash
75	# Example for a CORRECTION → ERROR_FIX
76	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
77	--session-id "$SESSION_ID" \
78	--type "ERROR_FIX" \
79	--context "what this relates to" \
80	--tags "perception,correction,topic" \
81	--confidence "high" \
82	--content "The actual learning: X was Y because Z" \
83	--json)
84
85	# Example for a REALIZATION/INSIGHT → CODEBASE_PATTERN
86	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
87	--session-id "$SESSION_ID" \
88	--type "CODEBASE_PATTERN" \
89	--context "what this relates to" \
90	--tags "perception,insight,topic" \
91	--confidence "high" \
92	--content "The actual learning: X was Y because Z" \
93	--json)
94
95	# Example for a DEBUGGING_APPROACH → WORKING_SOLUTION
96	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
97	--session-id "$SESSION_ID" \
98	--type "WORKING_SOLUTION" \
99	--context "debugging methodology" \
100	--tags "perception,debugging,approach" \
101	--confidence "high" \
102	--content "The actual learning: X was Y because Z" \
103	--json)
104	```
105
106	### Step 5: Output Summary
107
108	```
109	Session: $SESSION_ID
110	Thinking blocks analyzed: X
111	Perception signals found: Y
112	Learnings stored: Z
113
114	Stored:
115	- REALIZATION: "summary..."
116	- CORRECTION: "summary..."
117	```
118
119	## Quality Criteria
120
121	Include:
122	- Mental model shifts ("X works differently than I thought")
123	- Error root causes discovered ("the issue was schema mismatch")
124	- Approach corrections ("I was wrong about...")
125	- Surprising behaviors ("unexpected that...")
126
127	Exclude:
128	- Procedural planning ("Let me try X next")
129	- Simple task execution ("I'll read the file")
130	- Confirmations ("Good, that worked")
131	- Generic debugging ("Let me add logging")
132
133	## Example Extractions
134
135	### Good: CORRECTION
136	```
137	Thinking: "--depth: Exists on context (default 2) and impact (default 3) commands but NOT on tree. I was wrong about tree."
138
139	Learning:
140	- Type: CORRECTION
141	- Summary: --depth parameter exists on context/impact commands but NOT on tree command
142	- Context: tldr CLI usage - correcting assumption about which commands support --depth
143	```
144
145	### Good: INSIGHT
146	```
147	Thinking: "Now I see the issue. The code checks if (parsed.layers) but the actual JSON has entry_layer, leaf_layer, etc."
148
149	Learning:
150	- Type: INSIGHT
151	- Summary: Schema mismatch - code expect

People who liked this also viewed

6 picks

Type

memory-extractor

3.9kstars297forks

View on GitHub

How to install memory-extractor?

parcadei/continuous-claude-v3/memory-extractor

$curl -o .claude/agents/memory-extractor.md https://raw.githubusercontent.com/parcadei/Continuous-Claude-v3/HEAD/.claude/agents/memory-extractor.md

Installs into the current project.

Summary

Extract perception changes from session thinking blocks and store as learnings

Files · 1

View on GitHub

.claude/agents/memory-extractor.md

1	# Memory Extractor Agent
2
3	You extract perception changes from Claude Code session transcripts - the "aha moments" where understanding shifts.
4
5	## Philosophy
6
7	> "A point of view is worth 80 IQ points" - Alan Kay
8
9	We're looking for mental model shifts, not just error→fix pairs:
10	- Realizations: "Oh, X was actually Y"
11	- Corrections: "I was wrong about..."
12	- Insights: "The pattern here is..."
13	- Surprises: "Unexpected that..."
14
15	## Input
16
17	You receive:
18	- `JSONL_PATH`: Path to session JSONL file
19	- `SESSION_ID`: Session identifier (optional, extracted from path if not provided)
20
21	## Process
22
23	### Step 1: Extract Thinking Blocks with Perception Signals
24
25	```bash
26	# Use the extraction script with filtering
27	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
28	--jsonl "$JSONL_PATH" \
29	--filter \
30	--format json) > /tmp/perception-blocks.json
31	```
32
33	This extracts only thinking blocks containing perception signals (actually, realized, the issue, etc.).
34
35	### Step 2: Check Stats
36
37	```bash
38	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/extract_thinking_blocks.py \
39	--jsonl "$JSONL_PATH" \
40	--stats)
41	```
42
43	If 0 blocks with perception signals, skip to Step 5 (output summary with 0 learnings).
44
45	### Step 3: Classify Perception Changes
46
47	Read the extracted blocks from `/tmp/perception-blocks.json` and classify each one:
48
49	\| Internal Type \| Maps To \| Signal \| Example \|
50	\|---------------\|---------\|--------\|---------\|
51	\| `REALIZATION` \| `CODEBASE_PATTERN` \| Understanding clicks \| "Now I see that X works by..." \|
52	\| `CORRECTION` \| `ERROR_FIX` \| Was wrong, now right \| "I was wrong about --depth flag" \|
53	\| `INSIGHT` \| `CODEBASE_PATTERN` \| Pattern discovered \| "The issue is schema mismatch" \|
54	\| `DEBUGGING_APPROACH` \| `WORKING_SOLUTION` \| Meta-learning about how to debug \| "Test underlying command before wrapper" \|
55
56	Valid store_learning.py types:
57	- `FAILED_APPROACH` - Things that didn't work
58	- `WORKING_SOLUTION` - Successful approaches
59	- `USER_PREFERENCE` - User style/preferences
60	- `CODEBASE_PATTERN` - Discovered code patterns
61	- `ARCHITECTURAL_DECISION` - Design choices made
62	- `ERROR_FIX` - Error→solution pairs
63	- `OPEN_THREAD` - Unfinished work/TODOs
64
65	For each block that represents a genuine perception change (not just procedural planning), extract:
66	- Type (use the "Maps To" column for the `--type` parameter)
67	- Summary (one clear sentence)
68	- Context (what was being worked on)
69
70	### Step 4: Store Each Learning
71
72	For each extracted perception change, use the mapped type from Step 3:
73
74	```bash
75	# Example for a CORRECTION → ERROR_FIX
76	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
77	--session-id "$SESSION_ID" \
78	--type "ERROR_FIX" \
79	--context "what this relates to" \
80	--tags "perception,correction,topic" \
81	--confidence "high" \
82	--content "The actual learning: X was Y because Z" \
83	--json)
84
85	# Example for a REALIZATION/INSIGHT → CODEBASE_PATTERN
86	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
87	--session-id "$SESSION_ID" \
88	--type "CODEBASE_PATTERN" \
89	--context "what this relates to" \
90	--tags "perception,insight,topic" \
91	--confidence "high" \
92	--content "The actual learning: X was Y because Z" \
93	--json)
94
95	# Example for a DEBUGGING_APPROACH → WORKING_SOLUTION
96	(cd $CLAUDE_PROJECT_DIR/opc && uv run python scripts/core/store_learning.py \
97	--session-id "$SESSION_ID" \
98	--type "WORKING_SOLUTION" \
99	--context "debugging methodology" \
100	--tags "perception,debugging,approach" \
101	--confidence "high" \
102	--content "The actual learning: X was Y because Z" \
103	--json)
104	```
105
106	### Step 5: Output Summary
107
108	```
109	Session: $SESSION_ID
110	Thinking blocks analyzed: X
111	Perception signals found: Y
112	Learnings stored: Z
113
114	Stored:
115	- REALIZATION: "summary..."
116	- CORRECTION: "summary..."
117	```
118
119	## Quality Criteria
120
121	Include:
122	- Mental model shifts ("X works differently than I thought")
123	- Error root causes discovered ("the issue was schema mismatch")
124	- Approach corrections ("I was wrong about...")
125	- Surprising behaviors ("unexpected that...")
126
127	Exclude:
128	- Procedural planning ("Let me try X next")
129	- Simple task execution ("I'll read the file")
130	- Confirmations ("Good, that worked")
131	- Generic debugging ("Let me add logging")
132
133	## Example Extractions
134
135	### Good: CORRECTION
136	```
137	Thinking: "--depth: Exists on context (default 2) and impact (default 3) commands but NOT on tree. I was wrong about tree."
138
139	Learning:
140	- Type: CORRECTION
141	- Summary: --depth parameter exists on context/impact commands but NOT on tree command
142	- Context: tldr CLI usage - correcting assumption about which commands support --depth
143	```
144
145	### Good: INSIGHT
146	```
147	Thinking: "Now I see the issue. The code checks if (parsed.layers) but the actual JSON has entry_layer, leaf_layer, etc."
148
149	Learning:
150	- Type: INSIGHT
151	- Summary: Schema mismatch - code expect

People who liked this also viewed

6 picks

Type