Anki Refine

Refine Obsidian Markdown h4 blocks that represent Anki notes.

Core Workflow

1. Treat the Obsidian h4 block as the source of truth for the Anki note.
2. Locate the Anki note block by either the supplied ^anki-... anchor or the supplied h4 heading text.
3. By default, do not write files. First provide the refined note in the chat for review.
4. Iterate in chat until the user approves the exact wording.
5. Only write back when the user explicitly gives a clear apply instruction, such as apply or write back.
6. When in doubt, treat the request as review/proposal-only. Never infer writeback permission from the fact that the user supplied exact replacement text.
7. When applying, replace only the matched h4 block. Do not modify unrelated notes.

When rewriting note content, use the ankify skill for card quality and note format. This skill controls locating, chat review, and scoped write-back.

Locating the Note

Preferred locators:

• ^anki-... anchor: globally unique and most reliable.
• #### ... h4 heading text: acceptable when the user provides the exact heading and it is unique in the vault.

Prefer the narrowest known Markdown file scope. If the user names a .md file, the recent context clearly identifies the note file, or a nearby note was just edited in the same file, run rg directly against that .md file first. Do not start with a vault-wide search unless the target file is unknown.

Use literal search for an anchor:

rg -n "\^anki-123" "path/to/note.md"

Use literal search for a h4 heading:

rg -n -F "#### exact heading text" "path/to/note.md"

If the .md file is unknown, then search the smallest likely folder first, such as ddca/, before falling back to ..

After finding the target, read the full h4 block: from the matched #### heading through the line before the next #### heading, or EOF. If locating by h4 heading, confirm the full heading line is an exact match before applying. If locating by anchor, first find the preceding #### heading. Preserve the anchor line unless the user explicitly asks to remove it.

If multiple matches exist, show the candidate file paths/headings and ask the user which one to use. Do not write back unless the source h4 block is uniquely identified.

Local Editing Conventions

• Keep Obsidian wiki image links intact.
• Follow the user's punctuation rule: use English half-width punctuation in all Chinese text.

Applying Back

Before editing, restate which file and h4 heading will be replaced. Use a scoped edit that only replaces the selected h4 block. Clear Chinese instructions meaning write back, replace, or apply are also valid apply instructions.

After editing:

• If the original block had an anchor, check that it still exists.
• Check that no Chinese full-width punctuation was introduced.
• Briefly report the changed file and heading.