cmd-sync
/cmd-sync
Worklog vault command /cmd-sync. Use when the user runs /cmd-sync (or asks to update DEV_STATUS from this chat): updates Today, Yesterday and Ongoing in LLM/DEV_STATUS.md from the chat context.
- Author
- zelvet-velvet ↗
- Repository
- folio ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Worklog vault command /cmd-sync. Use when the user runs /cmd-sync (or asks to update DEV_STATUS from this chat): updates Today, Yesterday and Ongoing in LLM/DEV_STATUS.md from the chat context.
Original author description
Worklog vault command /cmd-sync. Use when the user runs /cmd-sync (or asks to update DEV_STATUS from this chat): updates Today, Yesterday and Ongoing in LLM/DEV_STATUS.md from the chat context.
How it works
SKILL.md has no level-two headings · 16 lines, 358 words
SKILL.md preview
---
name: cmd-sync
description: Worklog vault command /cmd-sync. Use when the user runs /cmd-sync (or asks to update DEV_STATUS from this chat): updates Today, Yesterday and Ongoing in LLM/DEV_STATUS.md from the chat context.
---
# /cmd-sync
Target: `LLM/DEV_STATUS.md` in the vault (vault root: this skill's folder resolved with `realpath`, three levels up).
- **Read first**: Read `DEV_STATUS.md` right before editing. The user may have changed or rolled back content in Obsidian; never restore rolled-back content.
- **Update** `Today`, `Yesterday` and `Ongoing` from the chat context (use `[x]` for done, `[>]` for in-progress). Finished Ongoing items move to `LLM/PROGRESS_ARCHIVE.md` only through `/cmd-notes-sync` (feature `archive`); without it they stay in Ongoing until the user clears them.
- **Callout format**: Each section body sits in a foldable callout under its heading (headings stay: the outline, links and `rollover.py` use them).
- `Today`: `> [!todo]+ N items` (`[!done]+` when every item is `[x]`). Empty `Today` = heading only, no callout.
- `Yesterday`: `> [!abstract]- N items` (written by `rollover.py`).
- `Ongoing` sections (each `###`): `> [!todo]- N open` (N = items marked `[ ]`, `[>]`, `[!]`, `[?]`, `[/]`, nested ones included).
- Every body line starts with `> `; nested items use 4 spaces per level after it (8 spaces does not render as a list inside a callout). Leave a blank line between a callout and the next `---`. Do not count by hand: after editing, run `python3 Tools/status/counts.py`, which rewrites every callout type and count.
- **Date**: Keep the date in the `Today` heading (`## 🚀 Today's Progress (YYYY-MM-DD)`) right. If it is an earlier day and `Today` has items, run `/cmd-rollover` first or ask; if empty, just set it to today.
- **Keep it concise** (no count limit): state the result, not the steps; no file lists, offsets or function chains unless they are the point. Details belong in the vault notes; link the note name instead.
- **Stale-note hint** (read-only, last step): From the items just written, name the vault notes that probably need an update (by feature, command code, function or file name; search the vault) and list them in the notification as `**[Notes to review]** <note>, <note>`. Do not edit them here: that is `/cmd-notes-sync` when the vault has it, otherwise a separate request.
- **Notification**: at the very end, only for modified sections, e.g. `**[Today's Progress]** Updated in DEV_STATUS.md`.
Versions
The database has no other skills named cmd-sync.
Database snapshot: 13.11.2026 · package version 6564e9f81ca4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86cmd-notes-sync
Worklog vault command /cmd-notes-sync [YYYY-MM-DD]. Use when the user runs /cmd-notes-sync: brings the vault notes describing the day's work up to date against the code, then moves finished Ongoing items of DEV_STATUS.md to PROGRESS_ARCHIVE.md. - 86cmd-weekly-report
Worklog vault commands /cmd-weekly-report and /cmd-weekly-report sync. Use when the user runs either, or asks to update the weekly report: rebuilds or updates LLM/WEEKLY_REPORT.md (Traditional Chinese) from DEV_STATUS.md or the chat. - 100cmd-plan-store
Capture the current conversation's plan, decisions, and action items into a structured markdown file in the project's plans/ directory. Triggers on "store this plan", "save this plan for later", "document this for later", "write up what we discussed", "create a plan file", or "/cmd-plan-store". - 100daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history.… - 90cmd-session-commit
Capture learnings from the current coding session and update AGENTS.md. Use when the user asks to close the loop, run session-commit, record best practices, or update agent instructions based on recent work. - 100mega-cmd
Use this skill for MEGA cloud storage, encrypted file management, and workflows involving file organization, sharing, search, sync, backup, bulk transfer to/from MEGA, or MEGA automation.