zk-mergelisted

# zk-merge ## When to use Use when the user asks to remove and/or close worktrees, merging notes, completing tasks, archiving to zk, or capturing results of an extended working session. Collect context from common locations such as `.opencode/`, `AGENT_CONTEXT.md`, `.serena`, `docs/`, diagrams, and newly added markdown files. The context **must be relevant to recent completed work**. Write a summary to a single well-organized Zettelkasten note keyed to a issue tracker key e.g. Jira issue key, github issue id, or a session summary (<= 8 words). ## Step 1: Identify an issue key or summarize ## Step 2: Review memory and docs Check serena memories, opencode memories, or other memories added during the session for relevant context. Review any new markdown files added to the project during the session, as well as any diagrams created or updated. Review any newly added allium files added. ## Step 3: Check for an Existing zk Note ```bash find "$ZK_NOTEBOOK_DIR/projects" -name "<JIRA-KEY>_*.md" 2>/dev/null ``` - **Found** → note the path; you will **append** to it. - **Not found** → you will **create** a new note. ## Step 4: Parse content Summarize each file found — extract what matters for future reference, not a verbatim copy. For all diagrams, reference from assets directory with relative path, do not embed as base64 or inline.: - `.d2` - Mermaid - Binary images (`.png`, `.svg`) Note that the memory filename reflects the topic. ## Step 5: Compose the Note ###