bug-hunting

Identify and reproduce bugs in Searchlite across CLI, HTTP, embedded API, wasm, and ffi.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/davidkelley/searchlite --skill bug-hunting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-hunting
Source: https://github.com/davidkelley/searchlite/tree/main/.codex/skills/bug-hunting
Command: npx skills add https://github.com/davidkelley/searchlite --skill bug-hunting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined workflow to identify, reproduce, and fix bugs in Searchlite, reducing regression risk and improving durability.

Core Features & Use Cases

  • Discovery and scoping: define affected surfaces (CLI, HTTP, embedded API, wasm, ffi) and failure mode.
  • Reproduction-first fixes: require minimal reproducible case and regression tests.
  • Durable changes: preserve WAL/manifest logic, atomic commits, and proper testing.
  • Use Case: When encountering incorrect results, crashes, or intermittent failures, apply this skill to structure debugging and regression testing.

Quick Start

Follow the discovery and reproduction steps to build a minimal repro artifact and guide bug-fix plan.

Frequently Asked Questions about bug-hunting

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

FAQPage Schema
How do I structure debugging and regression testing for intermittent failures across different API surfaces?

To structure debugging and regression testing, you first scope the affected surface (CLI, HTTP, embedded API, wasm, ffi), then build a minimal reproducible case to guide the fix plan and verify durability invariants.

What is the best way to reproduce bugs to ensure durable fixes without causing regressions?

The best way to reproduce bugs for durable fixes is to enforce a reproduction-first workflow that requires a minimal reproducible case, generates regression artifacts, and preserves WAL and manifest logic during atomic commits.

How does a bug-hunting workflow handle WAL and manifest logic during fixes?

A bug-hunting workflow handles WAL and manifest logic by enforcing durability invariants throughout the fix process, ensuring that atomic commits and proper testing are preserved to prevent future regressions.

Can I use this regression testing approach for crashes in both wasm and ffi surfaces?

Yes, you can use this regression testing approach for crashes in both wasm and ffi surfaces. The workflow explicitly scopes discovery and failure modes across CLI, HTTP, embedded API, wasm, and ffi boundaries.

Why does my debugging process need a minimal reproducible case before outlining a fix plan?

Your debugging process needs a minimal reproducible case because it creates reliable regression artifacts that document the root cause, enabling a precise fix plan and accurate verification steps without guesswork.