lumi-reset

Reset wiki content and operational state after dry-run plan and yes confirmation.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill lumi-reset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lumi-reset
Source: https://github.com/tronghieu/lumina-wiki/tree/main/src/skills/core/reset
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill lumi-reset

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents accidental loss of your Lumina-Wiki knowledge base and operational progress by forcing a plan-before-destruction reset with explicit confirmation.

Core Features & Use Cases

  • Scoped destructive reset with dry-run: Always generates a deletion plan first, then executes only after the user types the literal word yes.
  • Targets specific storage areas safely: Clears wiki pages, raw sources, operational state checkpoints, or a combined wiki+state cleanup without touching raw unless explicitly requested.
  • Path-safety and operational logging: Relies on the underlying reset script for path-safety checks and writes a reset entry to the wiki activity log when appropriate.

Quick Start

Ask to wipe the wiki by scoping it to wiki and confirming with yes after the dry-run plan is shown.

Frequently Asked Questions about lumi-reset

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

FAQPage Schema
How do I safely reset wiki content and operational state without losing data accidentally?

Safe wiki and state resets require a dry-run deletion plan first, followed by explicit chat confirmation typing the literal word yes before execution. This prevents accidental loss by forcing a plan-before-destruction workflow with scoped cleanup targets.

What is a dry-run reset and when do I need it for state management?

A dry-run reset generates a deletion plan showing exactly what will be removed without executing anything. You need it for state management recovery scenarios like restarting a stuck ingest, clearing checkpoints, or beginning with a clean slate for wiki and state files.

How to clear wiki pages and raw sources while keeping operational state checkpoints intact?

Clear wiki pages and raw sources by scoping the reset to wiki only. The scoped destructive reset targets specific storage areas safely, ensuring operational state checkpoints remain untouched unless a combined wiki+state cleanup is explicitly requested.

Can I restart a stuck ingest by clearing checkpoints without deleting my wiki knowledge base?

Yes, you can restart a stuck ingest by scoping the reset to state files only. This clears operational state checkpoints while preserving wiki content, requiring a dry-run plan and explicit yes confirmation before executing the destructive reset.

What are the limitations of using a scoped destructive reset for file deletion safety?

Scoped destructive resets require selecting an unambiguous scope and running in dry-run mode first. Limitations include needing the literal confirmation word yes to proceed, and resets write an activity log entry only when applicable for path-safety tracking.

Does the wiki cleanup process support combined wiki and state file recovery?

Wiki cleanup supports combined wiki and state recovery by selecting a combined wiki+state cleanup scope. The process runs reset.mjs in dry-run mode first, requires explicit yes confirmation, then executes the non-dry-run reset while writing a reset entry to the activity log.