From socialforge
Re-reads a calendar source (Notion, Drive, or file) to pick up changes, shows a diff, and updates calendar-data.json after confirmation. Accepts optional --brand and --source flags.
How this command is triggered — by the user, by Claude, or both
Slash command
/socialforge:sync-calendar [--brand <name>] [--source <path-or-url>]The summary Claude sees in its command listing — used to decide when to auto-load this command
# Sync Calendar Re-read the calendar source to pick up changes (new posts, modified briefs, removed posts). ## Process 1. Re-parse the calendar source (same format as original) 2. Compare with current calendar-data.json 3. Show diff: new posts, modified posts, removed posts 4. Confirm changes with user before applying 5. Update calendar-data.json 6. Re-run asset matching for new/modified posts only
Re-read the calendar source to pick up changes (new posts, modified briefs, removed posts).
npx claudepluginhub indranilbanerjee/socialforge/obsidian-calendarReads calendar into a snapshot note (agenda), also supports reconcile (vault vs calendar gaps), meeting (event to note), and schedule (task to event).
/content-calendarGenerates or updates an editorial content calendar from strategy and campaign files. Also supports adding, rescheduling, and exporting entries.
/brand-syncSyncs brand-brief.md between the current project and an external vault (Obsidian or plain directory), detecting conflicts by timestamp and offering push/pull/merge actions.
/kb-syncRuns deterministic KB maintenance for an Obsidian project — refreshes scaffold integrity, registry, index, daily note, and runtime binding summary. Accepts a scope argument.
/syncTwo-way sync between Nemp Memory and CLAUDE.md: imports user-written context into Nemp, detects conflicts with project state, and exports back. Also supports --import-only, --export-only, and --check flags.
/qaCompares each page in a WXR export against the original source site, reports content gaps, and optionally fixes discrepancies.