build-and-test
Build the Wassette workspace and run its test suite with the just recipes — debug and release builds, example and test components, and the combined unit plus documentation tests. Use when compiling Wassette, building example components, or running and debugging tests.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 976
- Forks
- 78
01 前言 Front Matter
- name
- build-and-test
- description
- Build the Wassette workspace and run its test suite with the just recipes — debug and release builds, example and test components, and the combined unit plus documentation tests. Use when compiling Wassette, building example components, or running and debugging tests.
- allowed-tools
- Bash, Read, Write, Edit, Glob, Grep
03 SKILL.md 正文
build-and-test skill
Build Wassette and run its tests through the just recipes defined in the
repository Justfile. Prefer these recipes over raw cargo invocations so the
WebAssembly component prerequisites are built automatically.
Prerequisites
- Rust: the version pinned in
rust-toolchain.toml(nightly is required only for formatting). - Cargo: Rust's package manager.
- Just: the command runner used for every development task.
- Node.js: only needed for the MCP Inspector when debugging.
- mdBook: only needed to build documentation.
Building
just build # Debug build (default)
just build release # Release build
just build-examples # Build the example components under examples/
just clean # Remove build artifacts
Testing
just test # Build test components, then run all tests
just build-test-components # Pre-build only the test components
just clean-test-components # Remove test-component artifacts
just test runs both unit tests and documentation tests, and automatically
builds the WebAssembly components the tests depend on. When a test fails because
a component is stale, run just clean-test-components and retry.
Notes
- Run the smallest recipe that covers your change; escalate to a full
just testonly when targeted checks pass but you need broader coverage. - After changing dependencies in a
Cargo.toml, rebuild before testing. - Follow the
rust-code-styleskill for formatting and linting, and validate server behavior with themcp-inspector-testingskill before committing.
04 同仓库更多 Skills
rust-code-style
Write idiomatic, well-structured Rust for Wassette — single-responsibility design, anyhow error handling, Arc/Mutex for shared state, and the required formatting and linting with cargo +nightly fmt, cargo clippy, and cargo machete. Use when adding or refactoring Rust code in this repository.
pull-request
Write concise, focused pull request descriptions for Wassette — at most three sentences on the what and why, with an explicit note on any breaking public-API change and how users adapt. Use when opening or editing a Wassette pull request.
mcp-inspector-testing
Validate Wassette changes end-to-end by running the MCP server with just and driving it with the MCP Inspector CLI over Streamable HTTP — listing tools, resources, and prompts, and calling tools. Use before committing server changes or when debugging tool exposure and behavior.
documentation
Build, serve, and write Wassette's mdBook documentation under docs/ — concise, code-first prose, the multi-version URL layout, and navigation in SUMMARY.md. Use when editing docs/ pages or previewing the documentation site.
copyright-headers
Ensure every Rust (.rs) file in Wassette starts with the required Microsoft copyright header, using the idempotent scripts/copyright.sh helper. Use when adding new Rust files or when a copyright-header check fails.