bugbashlisted

# Bugbash (General Software) Systematically explore a software project, find issues, and produce a report with full reproduction evidence for every finding. This skill applies to CLIs, APIs, Backends, Libraries, and other non-web interfaces. ## Setup Identify the **Target** (e.g., a CLI binary, an API base URL, a Python package). | Parameter | Default | Example override | |-----------|---------|-----------------| | **Target** | _(required)_ | `./my-cli`, `http://localhost:8080`, `import mylib` | | **Output directory** | `/tmp/dogfood-output/` | `Output directory: ./qa-reports` | | **Scope** | Full project | `Focus on the auth middleware` | ## Workflow ``` 1. Initialize Set up output dirs, report file, build/start the software 2. Orient Discover surface area (help menus, API schemas, exported functions) 3. Explore Systematically test features, inputs, and edge cases 4. Document Record exact inputs, outputs, and logs for each issue 5. Wrap up Update summary counts, finalize report ``` ### 1. Initialize ```bash mkdir -p {OUTPUT_DIR}/logs {OUTPUT_DIR}/evidence ``` Create a `report.md` in the output directory and fill in the header fields. Include: - Target - Date - Environment Details (OS, language version) - Summary Counts (Critical, High, Medium, Low) If the software needs to be built or started (e.g., `npm run build`, `docker-compose up`, `cargo build`), do that now. Keep track of the startup logs and run servers in the background if necess