Menu
Build and run DuckDB extension tests. Supports running all tests or a specific test file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guidance for writing, rewriting, reviewing, or outlining database systems research papers for VLDB, SIGMOD, PVLDB, CIDR, and similar venues. Use when working on paper structure, introductions, contributions, research questions, evaluation sections, figures, tables, related work, limitations, or reviewer-facing clarity for systems papers.
Multi-perspective code review of the most recent commit. Launches 5 parallel review agents covering correctness, reliability, performance, simplicity, and style. Reports findings with severity and confidence scores.
Structured feature planning with interrogation rounds and confirmation gate. Use when starting a non-trivial feature to align on requirements, scope, and edge cases before writing code.
Subsystem-by-subsystem codebase audit. Discovers source directories, reviews each from 5 perspectives, and produces prioritized findings. Use for periodic quality sweeps or before releases.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Reference for SIMD, vectorized query execution, and compiled query execution in database systems. Auto-loaded when discussing SIMD intrinsics, vectorization, query compilation, DuckDB execution model, pipeline breakers, morsel-driven parallelism, vector-at-a-time processing, or data-centric code generation.
| name | run-tests |
| description | Build and run DuckDB extension tests. Supports running all tests or a specific test file. |
GEN=ninja make 2>&1 | tail -5make test 2>&1
build/release/test/unittest "test/sql/<test_name>.test" 2>&1