knowie-migrate

Reconstructs a knowledge base from git history using parallel causal-masked sub-agents.

9|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/timcsy/semorphe --skill knowie-migrate-timcsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowie-migrate
Source: https://github.com/timcsy/semorphe/tree/main/.claude/skills/knowie-migrate
Command: npx skills add https://github.com/timcsy/semorphe --skill knowie-migrate-timcsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running projects lose the reasoning behind their decisions: the knowledge base drifts out of date, old structures no longer match current conventions, and the 'why' behind past choices is buried in git history. This Skill rebuilds a project's knowledge base by replaying its git history, recovering each decision's rationale without contaminating it with hindsight. ## Core Features & Use Cases - Encoder-decoder reconstruction: A bidirectional pass over the whole git history emits only structure (slices, transitions, tombstones), then parallel causal-masked sub-agents recover each slice's 'why' blind to its own future. - Transition vs tombstone classification: Distinguishes decisions that were in force then changed (numbered history entries) from options considered and declined (grouped tombstones) and knowledge-only projection edits (no transition). - Rumination loop: Re-reads the assembled base against git as fixed evidence, running judge passes and human-in-the-loop denoising until the structure converges. - Use Case: A team adopting a new knowledge-base structure runs this Skill on their repository; it walks first-parent merges, replays each era as the developer would have recorded it, and produces a migrated base with dated history entries, episodes, and drafts in the project's original language. ## Quick Start Ask the AI to run the knowie-migrate skill to check this knowledge base for structure drift and rebuild it from git history.

Frequently Asked Questions about knowie-migrate

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

FAQPage Schema
How do I migrate a knowledge base to a new structure using git history?

Run this Skill, which detects drift via the structureVersion field and folder names, then replays the git history slice by slice. Each slice is processed by a causal-masked sub-agent that recovers the original reasoning, and the results are merged into the new structure.

What is causal masking in knowledge base reconstruction?

Causal masking means each sub-agent sees only its slice's past—specs, commit messages, and contemporaneous knowledge—never the final state of the repository. This prevents rationalizing outcomes with hindsight, so recovered 'why' reflects what the author actually knew at the time.

Does this work on a repository without git history?

It degrades gracefully: with no git history or a too-shallow clone, it falls back to a single current-state-vs-canon pass. In that mode no causal masking is possible, and the Skill explicitly says so.

What is the difference between a transition and a tombstone in decision history?

A transition is a decision that was in force and later changed, recorded as a numbered history entry with the old one marked superseded. A tombstone is an option considered but never adopted, grouped into a catalog rather than dressed up as a transition.

Can the reconstruction run slices in parallel?

Yes. Because transition detection is lifted to the bidirectional encoder, each masked slice only produces local content and local why, needing no accumulated state. Independent slices therefore run in parallel with the same result as sequential execution.