wiki-clear-ingest-batches

Delete batch-import and batch-log files from the .import directory after user confirmation.

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-clear-ingest-batches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-clear-ingest-batches
Source: https://github.com/rijnb/knowledge-base-wiki/tree/main/.junie/skills/wiki-clear-ingest-batches
Command: npx skills add https://github.com/rijnb/knowledge-base-wiki --skill wiki-clear-ingest-batches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When using the LLM-maintained knowledge base ingestion workflow, leftover batch-import and batch-log files in the .import/ directory can clutter your workspace, and you need a safe, confirmed way to clear these files or abort an in-progress ingest without risking accidental data loss.

Core Features & Use Cases

  • Safe Batch Clearing: Deletes all batch-import-* and batch-log-* files in .import/ only after explicit user confirmation to prevent unintended deletions.
  • Abort Option: Lets you cancel the operation entirely if you decide not to proceed with clearing files.
  • Use Case: If you ran a batch ingest of raw notes and want to reset the import state to start fresh, or need to cancel an ongoing ingest process, this skill handles the cleanup safely.

Quick Start

Ask the AI to clear all ingestion batch files from the .import directory.

Frequently Asked Questions about wiki-clear-ingest-batches

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

FAQPage Schema
How do I clean up leftover batch-import files in my knowledge base .import directory?

To clean up leftover batch-import files, the skill deletes batch-import-* and batch-log-* files specifically within the .import directory, requiring explicit user confirmation beforehand to prevent accidental data loss.

How can I abort an in-progress knowledge base ingest workflow safely?

You can abort an in-progress knowledge base ingest workflow by triggering the batch cleanup operation and choosing the abort option. This cancels the ongoing ingest process and clears associated batch files safely.

When do I need to reset the import state for an LLM-maintained knowledge base?

You need to reset the import state when leftover batch-import and batch-log files clutter your workspace, such as after running a batch ingest of raw notes and wanting to start fresh without residual import data.

Does clearing ingestion batch files require manual confirmation to prevent data loss?

Yes, clearing ingestion batch files requires explicit user confirmation before deleting any batch-import-* or batch-log-* files, ensuring you can abort the operation entirely and prevent unintended deletions.

What happens to batch-log files during an import reset?

During an import reset, batch-log-* files are deleted from the .import directory alongside batch-import-* files. Both file types are removed only after you explicitly confirm the cleanup action.