Build, debug, test, and ship DuckDB C++ extensions with CMake and CI pipelines.
npx skills add https://github.com/cofin/flow --skill duckdb-extension
Please help me install this Agent Skill. Skill: duckdb-extension Source: https://github.com/cofin/flow/tree/main/skills/duckdb-extension Command: npx skills add https://github.com/cofin/flow --skill duckdb-extension
This Skill streamlines the development of DuckDB C++ extensions, ensuring they are built, tested, and shipped according to best practices.
extension_config.cmake and CMakeLists.txt.Makefile and CI targets for building extensions.Use the duckdb-extension skill to confirm the build wiring for the 'my_duckdb_extension' project.
High-intent search queries and answers about installing and using this skill.
To build a DuckDB C++ extension, validate and configure your `extension_config.cmake` and `CMakeLists.txt` files to ensure correct build wiring. This process leverages existing Makefile and CI targets for reproducible builds of loadable and static extension targets.
Running SQL tests for a DuckDB extension involves executing unit and integration tests located in the `test/*.test` directory. This ensures your C++ extension functions correctly and satisfies requirements for comprehensive testing before distribution.
A DuckDB extension repository requires `extension_config.cmake`, `CMakeLists.txt`, `src/*.cpp` source files, `test/*.test` scripts, and GitHub Actions pipelines. These files enable reproducible builds, testing, and efficient binary distribution.
Validating GitHub Actions pipelines for DuckDB extension binaries involves checking the CI configuration to ensure robust release processes. This step confirms that loadable and static extension targets are packaged and distributed efficiently.
Yes, the DuckDB extension build process supports both loadable and static extension targets. It ensures reproducible builds and efficient distribution by validating the CMake configuration and leveraging existing CI targets.
DuckDB C++ extension builds often fail due to incorrect `extension_config.cmake` or `CMakeLists.txt` configuration. Validating these files against current best practices ensures proper build wiring and resolves reproducible build issues.
EnigmaWUAutomate C/C++ project setup with CMake, Google Tests, and sanitizers.
data-desk-ecoAutomate notebook back-end build and deployment workflows with GitHub Actions.
hector-mannyStreamline C# unit and integration testing with xUnit and NSubstitute.
AlexandrePrevotConfigure and build the OrderParserProcessor C++ backend with CMake.