migrate-feedback-memories

Route per-project feedback memories to capture, retain, or delete destinations via a bundled enumerator.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill migrate-feedback-memories-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-feedback-memories
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/migrate-feedback-memories
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill migrate-feedback-memories-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feedback memories accumulate across per-project memory stores on a machine, mixing generalizable lessons with redundant restatements and purely local facts. This Skill routes each memory to its proper destination so propagating lessons reach the shared knowledge base instead of staying siloed. ## Core Features & Use Cases - Machine-wide enumeration: A bundled Node helper lists every feedback memory across all memory stores under ~/.claude/projects/, with optional scoping to a single store via --memory-store. - Three-way routing: Each memory is classified as Capture (generalizable lesson recorded as a capture-feedback event in the codeassembly KB), Retain (genuinely local fact), or Delete (redundant restatement), with origin-based dedup against existing KB events. - Confirm-by-default batch flow: The routing plan is presented for review before execution, with an --auto flag to skip confirmation, and deletions reconcile each store's MEMORY.md index. - Use Case: After weeks of agent sessions, run the migration to move reusable behavioral lessons from scattered project memory stores into the shared knowledge base while cleaning out redundant memories. ## Quick Start Ask the agent to migrate this machine's feedback memories, optionally scoping to one project store or adding --auto to skip the review step.

Frequently Asked Questions about migrate-feedback-memories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate feedback memories into a shared knowledge base?

Run the skill's enumerate subcommand to list all feedback memories, classify each as capture, retain, or delete, then record captures as capture-feedback events in the codeassembly KB store. Successful captures and redundant memories are removed in a single batched deletion pass.

How do I process only one project's memory store?

Pass --memory-store <name> to scope the run to a single store, using either the directory name or the project label. Unknown names return a no-such-memory-store error and ambiguous labels list the matching stores.

What Node version does the feedback memory migration require?

The bundled helper requires Node 24 or later, matching the version floor of the @williamthorsen/kb package it builds on.

When should a feedback memory be deleted instead of captured?

Delete only when the memory restates a rule that shared guidance or a prior capture already codifies with no new signal. A memory narrating a violation of existing guidance is captured with the mistake tag instead, since it is fresh evidence the guidance is not taking effect.

What happens if I re-run the migration on the same machine?

A re-run is a no-op for processed stores because captured and deleted memories are removed, leaving only retained local memories. Origin-based dedup also prevents double-counting lessons already captured on earlier runs or other machines.