name: v-sync-logger description: Automated "4-Doc Rule" synchronization (CHANGELOG, PROJECT_STATUS, APP_CONTEXT, README) and Git checkpointing. risk: safe date_added: "2026-03-29"

v-sync-logger (Vedic Sync Logger)

Overview

This skill automates the synchronization of the project's primary documentation and provides consistent Git versioning. It ensures the "Infinite Memory" remains accurate by updating history, state, and architecture in a single turn.

When to Use

• At the end of every significant task or feature implementation.
• When the user asks to "Sync logs" or "Update the 4-Doc Rule".
• After making architectural changes that need to be reflected in APP_CONTEXT.md.

Workflow

1. Extract Changes:

   • Parse the most recent entries in task.md (completed tasks [x]).
   • Review the current conversation history for "Major Updates".

2. Update CHANGELOG.md:

   • Identify the current version (e.g., [1.4.0]).
   • Append new entries under appropriate headers (### Added, ### Changed, ### Fixed).
   • Use the date of the session for new version entries if applicable.

3. Update PROJECT_STATUS.md:

   • Create a new ## 📅 Session Log: [Date] (Summarized Focus) block.
   • List the "Major Updates" clearly.
   • Define concrete "Next Steps" based on the remaining tasks in task.md.

4. Update APP_CONTEXT.md:

   • Synchronize the "Future Roadmap" if tasks were completed or new ones were planned.
   • If new key files or services were added, update the "Key File Map".
   • If the "Logic Index Table" needs updating due to new interpretation docs, do so now.

5. Update README.md:

   • Update the "Status" section (e.g., Phase 0 to Phase 1).
   • If new dependencies (npm install) or configuration keys (.env) were added, update the "Installation" and "Prerequisites" sections.
   • Ensure the "Tech Stack" reflects any shifts (e.g., adding New Models).

6. Brain Sync:

   • brain_store: Automatically store the session summary, major updates, and next steps into the Lob Brain database.
   • Title: Sync: [Date] - [Summary]
   • Tags: ['sync', 'logs', 'status']
   • Importance: 4 (Stable memory)

7. Git Checkpoint:

   • Execute a unified commit for the synchronization.
   • // turbo
   • git add . && git commit -m "Pulse: [Summary of the Log Sync]"
   • If the commit fails (e.g., no changes), inform the user that the docs were already in sync.

Output Expectations

• A confirmation that all three files were updated.
• The Git commit hash or confirmation of the checkpoint.
• A summary of the "Next Steps" prioritized for the next session.

Failure Shields

• DO NOT delete historical entries from CHANGELOG.md or PROJECT_STATUS.md.
• ALWAYS check for existing "Session Logs" for the current date before creating a new one to avoid duplication.
• NEVER commit without including the documentation updates in the same atomic commit.