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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 976
- Forks
- 78
01 前言 Front Matter
- name
- copyright-headers
- description
- 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.
- allowed-tools
- Bash, Read, Write, Edit, Glob, Grep
02 资源文件 4
- 参考文档references/adapter-system.md9.2 KB
- 参考文档references/configuration.md9.3 KB
- 参考文档references/custom-benchmarks.md6.9 KB
- 参考文档references/execution-backends.md9.1 KB
03 SKILL.md 正文
copyright-headers skill
All Rust (.rs) files in Wassette must begin with the Microsoft copyright
header, placed at the very top of the file and followed by a blank line before
any other content (including crate-level documentation and imports).
Required format
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT license.
Apply headers
Run the idempotent helper, which adds the header to any file missing it and leaves existing headers untouched, so it is safe to run repeatedly:
./scripts/copyright.sh
Verify
grep -q "Copyright (c) Microsoft Corporation" your_file.rs
Apply the header before committing new files; the format must match exactly as shown above.
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.
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.