What is the primary purpose of the Reweave skill?

Reweave revisits older notes in your repository to connect them with newer information, ensuring your knowledge base stays integrated and up-to-date.

How does Reweave differ from the /reflect command?

While /reflect typically focuses on current synthesis and forward connections, Reweave specifically handles the 'backward pass,' linking older content to the insights you've gained more recently.

What is 'Claim Sharpening' in Reweave?

Claim sharpening is a process where the skill evaluates if a note's title or core thesis is too vague and helps rewrite it into a more specific, arguable, and useful statement.

Can I use Reweave on a specific note?

Yes, you can invoke it using '/reweave [[note name]]' to target a specific document for a deep reconsideration against your current knowledge.

Reweave Knowledge Connector

Name: Reweave Knowledge Connector
Author: LopeWale

byLopeWale

0•

Content Management

Maintains and updates personal knowledge bases by creating backward connections between old notes and new insights.

Reweave is a specialized skill designed for the long-term maintenance of digital gardens, second brains, and technical documentation. It performs the 'backward pass' that standard updates often miss, revisiting existing notes that predate newer content to add relevant connections, sharpen claims, and suggest content splits. By utilizing dual discovery—combining semantic search with topic map exploration—Reweave ensures that your knowledge network remains a living, cohesive system rather than a collection of stale, isolated documents.

Key Features

010 GitHub stars

02Automated backward connection discovery for existing notes

03Claim sharpening to transform vague notes into specific insights

04Smart note splitting for documents covering too many claims

05Dual-path discovery using semantic search and topic map browsing

06Configurable processing depth for quick updates or deep reconsiderations

Use Cases

01Updating technical documentation to reflect new architectural changes

02Maintaining a 'Digital Garden' or long-term research repository

03Refining a second brain by linking older foundational notes to current projects

Key Features

010 GitHub stars

02Automated backward connection discovery for existing notes

03Claim sharpening to transform vague notes into specific insights

04Smart note splitting for documents covering too many claims

05Dual-path discovery using semantic search and topic map browsing

06Configurable processing depth for quick updates or deep reconsiderations

Use Cases

01Updating technical documentation to reflect new architectural changes

02Maintaining a 'Digital Garden' or long-term research repository

03Refining a second brain by linking older foundational notes to current projects