Process voice transcriptions in today's daily note
Processes voice transcriptions in daily notes by cleaning prose, applying corrections, and restructuring content.
npx claudepluginhub technicalpickles/pickled-claude-pluginsdate e.g. 2026-01-21Clean up voice transcriptions in a daily note. Works in phases with confirmation between each.
This command only works inside a vault.
Check if current directory is a vault:
ls -d .obsidian 2>/dev/null
If .obsidian/ not found in current directory or parents:
⚠ /second-brain:process-daily only works inside a vault.
You're currently in: {cwd}
Options:
1. Open your vault via symlink: ~/.claude/vaults/{name}
2. Use /second-brain:insight to capture from here
3. Use /second-brain:distill-conversation for end-of-session extraction
Stop execution - do not continue.
Read CLAUDE.md at vault root for:
If argument provided: Use as date (parse YYYY-MM-DD format) If no argument: Use today's date
date +"%Y-%m-%d"
Construct path from vault's daily note location (e.g., Fleeting/{date}.md).
If file doesn't exist, inform user and stop.
Read Glossary.md if it exists at vault root.
Parse correction mappings by category.
Read daily note. Report:
Loaded: Fleeting/2026-01-21.md
Glossary: Found ({N} known corrections)
Content: ~{N} words, {structured|unstructured}
Ready to process. Continue? [Yes] [Cancel]
Present corrections in batches by category:
### Tools & Software (Batch 1 of 4)
| # | Found | → Correction | Context |
|---|-------|--------------|---------|
| 1 | me's | mise | "started using me's" |
| 2 | Claude MT | CLAUDE.md | "added Claude MT" |
✓ Accept all | Enter numbers to reject | ? for more context
Categories:
After all batches, offer glossary update for new corrections.
Remove filler words, false starts, run-on sentences.
Preserve: conversational tone, first-person voice, meaning.
Show before/after preview for representative sections.
If note lacks structure, propose restructuring to match daily template:
## Action Items ← Top: high visibility
## Extracted Notes ← Links to permanent notes
## Log ← Structured events
## Quick Notes ← Bottom: append zone
Identify content substantial enough for permanent notes.
Criteria: substantial, reusable, standalone, reference-worthy.
Offer extraction with routing.