MicrosoftKnown publishermicrosoft/wassette/.agents/skills/build-and-test/SKILL.md

build-and-test

Skill977 starsChanged 3 months agoMITView on GitHub

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.

6 other projects use a version of this.

Adopted by

Most recently taken up by

thanhthanh11/claudeCodetheir own version, first seen Oct 25, 2026
google/boringssltheir own version, first seen Oct 20, 2026
microsoft/agent-frameworktheir own version, first seen Oct 13, 2026
huynhsontung/Screenboxtheir own version, first seen Oct 8, 2026
dotnet/runtimetheir own version, first seen Oct 8, 2026
BariBariGood/manzanastheir own version, first seen Aug 23, 2026

Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
dotnet/runtime★ 18ksame name
microsoft/agent-framework★ 15ksame name
huynhsontung/Screenbox★ 4.7ksame name
google/boringssl★ 2.3ksame name
BariBariGood/manzanas★ 22same name
thanhthanh11/claudeCode★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- copyright-headersSkill
- documentationSkill
- mcp-inspector-testingSkill
- pull-requestSkill
- rust-code-styleSkill

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Node.js: only needed for the MCP Inspector when debugging.
line 19
Distinctive:
mdBook: only needed to build documentation.
line 20
Very specific:
Run the smallest recipe that covers your change.
line 45
Very specific:
After changing dependencies in a Cargo.toml, rebuild before testing.
line 47
Very specific:
Follow the rust-code-style skill for formatting and linting, and validate server behavior with the mcp-inspector-testing skill before …
line 48

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

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 test only when targeted checks pass but you need broader coverage.
After changing dependencies in a Cargo.toml, rebuild before testing.
Follow the rust-code-style skill for formatting and linting, and validate server behavior with the mcp-inspector-testing skill before committing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free