session-sync

Rebuild project documentation and Serena memories to correct drift after code changes.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill session-sync-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-sync
Source: https://github.com/jrmatherly/spacebot/tree/main/.claude/skills/session-sync
Command: npx skills add https://github.com/jrmatherly/spacebot --skill session-sync-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures documentation and session memories do not drift from the codebase after feature work, migrations, refactors, or bug fixes by verifying, repairing, and committing only documentation and memory updates while avoiding staging unrelated code changes.

Core Features & Use Cases

  • Rebuild code-review graph: incrementally update or note missing graph state to keep review metadata accurate.
  • Reflect on session learnings: detect new modules, migrations, tools, or architecture changes to target checks.
  • CLAUDE.md and roadmap verification: confirm version, architecture summary, build and lint commands remain accurate.
  • Serena memory sync: read and apply targeted edits to five memories (project_overview, project_structure, style_and_conventions, suggested_commands, task_completion_checklist) using filesystem ground truth.
  • Safe commit workflow: run formatting checks, stage only doc/memory edits, and commit with a standardized message; skip or note missing surfaces gracefully.
  • Use case example: after finishing a feature and adding a migration, run the skill to update CLAUDE.md version references and Serena memories, then commit the drift fixes in a single docs commit.

Quick Start

Invoke the session-sync skill at the end of your work session with an optional scope hint, for example: /session-sync after adding WebSocket adapter + migration 043.

Frequently Asked Questions about session-sync

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

FAQPage Schema
How do I keep documentation in sync with code changes after a refactor?

Keeping documentation in sync involves verifying CLAUDE.md and memory surfaces against filesystem ground truth, staging only documentation edits, and committing drift fixes with a standardized message after substantive code changes.

What is documentation drift detection in software engineering?

Documentation drift detection is the process of identifying when project docs and memory surfaces become stale or inaccurate relative to the actual codebase following modules, migrations, tooling, refactors, or bug fixes.

How do I update Serena memories to match my latest project structure?

You update Serena memories by reading five specific memory surfaces—project_overview, project_structure, style_and_conventions, suggested_commands, and task_completion_checklist—and applying targeted edits based on current filesystem ground truth.

How to commit only documentation and memory updates without staging code changes?

To commit only documentation and memory updates without staging code changes, run formatting checks, stage exclusively the doc and memory edits, and commit using a standardized message while skipping unrelated code modifications.

When should I run a documentation sync workflow for my codebase?

You should run a documentation sync workflow at the end of a work session that involved substantive code changes such as adding new modules, database migrations, tooling updates, refactoring, or bug fixes where docs may be stale.

Does session-sync work without dependencies or external components?

Yes, session-sync operates without requiring external dependencies or components, functioning independently to verify CLAUDE.md, update Serena memories, and commit documentation fixes safely.