wiki-purge

Permanently removes a topic and its evidence from an Obsidian markdown wiki.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ehartye/wiki-master --skill wiki-purge-ehartye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-purge
Source: https://github.com/ehartye/wiki-master/tree/main/skills/wiki-purge
Command: npx skills add https://github.com/ehartye/wiki-master --skill wiki-purge-ehartye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deleting files does not actually remove a topic from a maintained wiki: leftover raw clippings get re-ingested, source URLs get rediscovered, and uncommitted deletions get undone by sync. This Skill closes every path by which a purged topic can return, in one reversible, committed transaction. ## Core Features & Use Cases - Planned, approved removal: Generates a removal plan listing every file to bin, collateral pages needing link repair, and blocking pages that would lose all evidence, requiring explicit approval before applying. - Reversible purge with manifest: Moves files to a retained recycle bin, records source declines, commits only the touched paths, and supports full restore by purge id without overwriting newer work. - Cross-machine reconciliation: A reconcile mode sweeps remnants of earlier purges, and the workflow detects orphaned git lineages where a purge could never reach other machines. - Use Case: A user asks to remove a self-help topic from their Obsidian vault; the Skill plans the purge, pins the correct seeds, bins 10 files, repairs 3 collateral pages' links, and verifies the broken-link count did not grow. ## Quick Start Ask the agent to purge a specific topic from the wiki, review the removal plan it presents, and approve it before anything is moved.

Frequently Asked Questions about wiki-purge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I permanently remove a topic from an Obsidian wiki?▼

Run the purge plan for the topic, review the seeds and collateral pages, get explicit approval, then apply. The purge moves files to a recycle bin, records source declines, repairs links on surviving pages, and commits only the paths it touched.

Why does a deleted wiki topic keep coming back?▼

Four causes resurrect topics: uncommitted deletions undone by sync, leftover raw clippings that re-ingest, source URLs that discovery re-clips, and commits made on an orphaned git lineage. Purge closes the first three; the fourth requires reconciling histories first.

Can a wiki purge be undone after it is applied?▼

Yes, restore by purge id puts everything back and commits. It never overwrites files that now exist at the original path, clears only the declines this purge recorded, and reports any manifest entries the bin cannot supply as missing.

What happens when a purge stops partway through?▼

The apply step reports files it could not move, usually due to Windows file locks, and stops before committing. Close whatever holds the files and run reconcile to finish in place; never re-run apply, which would start an empty second purge.

Why should purge verification not use the health score?▼

Purging an orphaned page removes an orphan penalty, so the score can rise even with unrepaired links. Dangling links are classified as deferred and unscored, so verification must compare the broken-links count against the pre-purge baseline instead.