القائمة
Rewrite the Obsidian daily journal for a selected day from existing plan/summary notes. Use when journal entries are missing, corrupted, or need regeneration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Backport existing plans into the Obsidian daily journal. Use when plans exist in the vault but are missing journal entries.
Estimate the scope and runtime of the frontmatter backfill — hardware specs, vault size, pending upgrades, and a calibrated time estimate. Read-only; nothing is modified.
Upgrade existing vault notes to the current frontmatter standard (type, date, duration_s, normalized model + context_window) so they appear in the managed Obsidian bases. Interruptible and resumable.
Display all configuration options with their effective value and which config layer set them.
Display current session details including ID, duration, turn counts, token usage, and tool stats.
Toggle session document capture on or off. Use /session on, /session off, or /session to toggle.
| name | rewrite-journal |
| description | Rewrite the Obsidian daily journal for a selected day from existing plan/summary notes. Use when journal entries are missing, corrupted, or need regeneration. |
Reconstruct the daily journal for a selected day by reading all plan, summary, and activity notes in the vault for that date. The existing journal file is backed up before rewriting.
Run the discovery script from the plugin root directory:
bun ${CLAUDE_PLUGIN_ROOT}/hooks/rewrite-journal.ts --list-days 2>/dev/null
Parse the JSON output. Each entry has: date, dayName, planCount, hasJournal, hasBackup.
Tell the user: "Found N days with plans in the vault."
If no days found, inform the user and stop.
List the available days, formatted as:
YYYY-MM-DD (DayName) — N plans [journal exists | no journal] [backup exists]
Use AskUserQuestion to let the user pick a day. Default to today if today is in the list.
If the selected day already has a backup file, warn the user that the existing backup will be overwritten.
Use AskUserQuestion with these options:
Run the script in dry-run mode:
bun ${CLAUDE_PLUGIN_ROOT}/hooks/rewrite-journal.ts --day=YYYY-MM-DD --dry-run [--skip-summarize] 2>/dev/null
Add --skip-summarize if the user chose fast text extraction.
Parse the JSON result and show: "Will rewrite journal for YYYY-MM-DD: N plans to process. Current journal will be backed up."
If there are errors, show them to the user.
Use AskUserQuestion to confirm:
Run the same command without --dry-run:
bun ${CLAUDE_PLUGIN_ROOT}/hooks/rewrite-journal.ts --day=YYYY-MM-DD [--skip-summarize]
Progress lines appear on stderr during summarization (e.g. [3/40] Summarized: 01-my-slug (plan)).
Parse the JSON result and display: "Rewrote journal for YYYY-MM-DD: N callouts created, M revisions written. Backup saved."
If there were errors, list them for the user.
Use AskUserQuestion with these options:
If the user chooses to remove:
bun ${CLAUDE_PLUGIN_ROOT}/hooks/rewrite-journal.ts --remove-backup --day=YYYY-MM-DD 2>/dev/null
Confirm removal to the user.