novel-sync

Sync approved chapter summaries into memory and rebuild the knowledge graph.

13|4|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TulanCN/vibe-noveling --skill novel-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: novel-sync
Source: https://github.com/TulanCN/vibe-noveling/tree/main/plugins/vibe-noveling/skills/novel-sync
Command: npx skills add https://github.com/TulanCN/vibe-noveling --skill novel-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual chapter synchronization and knowledge-graph updates are error-prone and time-consuming after a chapter passes quality checks.

Core Features & Use Cases

  • Updates memory/past.md with the chapter summary after verification.
  • Refreshes long-term threads and the chapter-level sync tracker to reflect progress and伏笔 states.
  • Rebuilds the knowledge graph index to keep entity data aligned with the latest writing.
  • Updates CLAUDE.md progress to reflect completed chapters and chapter titles when available.
  • Enforces human review and safety boundaries to prevent premature or speculative updates.

Quick Start

Run the novel-sync workflow after a chapter is approved to push summaries and progress into memory and the knowledge graph.

Frequently Asked Questions about novel-sync

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

FAQPage Schema
How do I sync completed novel chapters to a knowledge graph?

To sync completed novel chapters to a knowledge graph, this workflow scans approved chapter content, updates past.md and memory trackers, then rebuilds the knowledge graph index to align entity data with the latest writing.

What is the best way to track novel writing progress and foreshadowing states?

Tracking novel writing progress and foreshadowing states is handled by updating long-term threads and chapter-level sync trackers, linking past.md memory files with current chapter summaries to preserve narrative history.

How do I update memory files and CLAUDE.md progress after chapter approval?

Updating memory files and CLAUDE.md progress after chapter approval requires executing the sync workflow, which automatically pushes verified chapter summaries and titles into the designated memory management files.

Does the chapter synchronization workflow require human confirmation before updating memory?

Yes, the chapter synchronization workflow enforces human review and safety boundaries, requiring explicit human confirmation before updating any memory files or rebuilding the knowledge graph to prevent premature changes.

Can I use this knowledge graph sync to automatically update future planning documents?

No, you cannot use this knowledge graph sync to automatically update future planning documents; the workflow actively avoids speculative updates to future planning, strictly focusing on completed and approved chapter artifacts.

How does novel-sync rebuild the knowledge graph while preserving history?

Novel-sync rebuilds the knowledge graph while preserving history by scanning newly approved chapter artifacts, extracting updated entity data, and refreshing the index without overwriting the established past.md memory records.