verify-kb-indexing

Validate asynchronous Knowledge Base indexing pipelines for state machine consistency and error handling.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/bigbulgogiburger/rag-bio --skill verify-kb-indexing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-kb-indexing
Source: https://github.com/bigbulgogiburger/rag-bio/tree/main/.claude/skills/verify-kb-indexing
Command: npx skills add https://github.com/bigbulgogiburger/rag-bio --skill verify-kb-indexing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies the robustness and correctness of the Knowledge Base (KB) asynchronous indexing pipeline, ensuring data is processed reliably and errors are handled gracefully.

Core Features & Use Cases

  • Pipeline Verification: Checks state machine transitions, asynchronous processing patterns, and error handling.
  • Codebase Auditing: Validates critical components like text extraction, chunking, and vector storage interactions.
  • Use Case: After modifying the asynchronous indexing logic or thread pool configuration, run this Skill to confirm that documents transition correctly through states (UPLOADED, INDEXING, INDEXED/FAILED) and that errors during indexing are properly caught and logged, preventing data loss or corruption.

Quick Start

Run the verify-kb-indexing skill to audit the asynchronous KB indexing pipeline after code modifications.

Frequently Asked Questions about verify-kb-indexing

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

FAQPage Schema
How do I verify asynchronous KB indexing pipeline consistency after code changes?

You verify asynchronous KB indexing pipeline consistency by checking state machine transitions, @Async and @Transactional patterns, and afterCommit callbacks to ensure reliable document indexing and state transitions.

What causes documents to get stuck or lost during asynchronous knowledge base indexing?

Documents get stuck during knowledge base indexing when state machine transitions fail to propagate correctly, or when worker processes lack robust error handling and afterCommit callbacks to catch indexing failures.

How do I audit @Async and @Transactional patterns for safe text extraction and indexing?

Auditing @Async and @Transactional patterns for text extraction safety involves verifying correct propagation, afterCommit callbacks, and robust error management in worker processes to prevent data loss or corruption.

Does this pipeline verification check for correct HTTP response codes during document indexing?

Pipeline verification checks for correct HTTP response codes during document indexing, ensuring state transitions between UPLOADED, INDEXING, and INDEXED or FAILED states are handled gracefully with proper error management.

What are the limitations of asynchronous indexing pipelines when handling text extraction errors?

Asynchronous indexing pipelines with inadequate text extraction safety and poor error handling risk data corruption, as worker processes may fail to catch and log indexing errors or propagate state transitions correctly.