rust-skill-maintenance
Maintain this modular Rust skills system, including canonical content, manifests, references, profiles, generated adapters, migrations, examples, evaluations, releases, and compatibility. Use when changing the skills repository itself. Do not hand-edit generated adapters.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- rust-skill-maintenance
- description
- Maintain this modular Rust skills system, including canonical content, manifests, references, profiles, generated adapters, migrations, examples, evaluations, releases, and compatibility. Use when changing the skills repository itself. Do not hand-edit generated adapters.
02 资源文件 2
- 参考文档references/maintenance.md3.5 KB
- 其他skill.toml635 B
03 SKILL.md 正文
Maintain Rust Skills
Preserve canonical ownership
- Read
$rust-core, repository authoring instructions, architecture, source ledger, affected schemas, migration map, and existing evals. - Read maintenance workflow.
- Identify the stable skill and rule owner before editing. Route a rule instead of duplicating it.
Change the system
Author portable runtime content under skills/, organization preferences under
organizations/, repository choices in adoption output, external evidence in
the reference catalog, transformations in examples/, and behavior gates in
evals/.
Keep entry files concise and references selectively loaded.
Record the source, trust tier, revision, license posture, limitations, review date, and refresh rule for external guidance. Preserve stable IDs. Add migration notes before a rename, split, behavior change, schema change, or generated layout change.
Never edit generated/ directly. Regenerate it from the exact canonical source
state. Keep eval prompts isolated from graders and compare unchanged tasks
against a clean baseline or prior release before claiming improvement.
Validate and release
Run cargo xtask validate, cargo xtask generate --check, formatting, Clippy,
tests, script smoke tests, and applicable eval validation. Update installation,
maintenance, task maps, provenance, and release metadata together.
Output
Provide source-to-destination migration detail, retained behavior, behavior changes, compatibility impact, generated state, validation, eval evidence, and release implications.
04 同仓库更多 Skills
rust-unsafe-ffi
Design and review unsafe Rust, safe wrappers, manual Send or Sync, ABI boundaries, foreign ownership, callbacks, and FFI build integration. Use whenever unsafe code or a foreign interface is introduced, changed, or relied upon. Do not use unsafe merely to bypass borrow checking or for unmeasured optimization.
rust-testing
Select, implement, and assess Rust unit, integration, documentation, property, fuzz, snapshot, concurrency, unsafe, protocol, benchmark, and verification evidence. Use whenever behavior changes or claims need proof. Do not run every tool mechanically when the repository or risk makes it inapplicable.
rust-skill-maintenance
Maintain this modular Rust skills system, including canonical content, manifests, references, profiles, generated adapters, migrations, examples, evaluations, releases, and compatibility. Use when changing the skills repository itself. Do not hand-edit generated adapters.
rust-review
Review Rust diffs, commits, branches, and designs for actionable correctness, soundness, security, compatibility, concurrency, protocol, performance, testing, and maintainability risks. Use for review or pre-merge assessment. Do not modify code unless separately requested.
rust-repository-onboarding
Inspect, interview, profile, configure, and install the modular Rust engineering skills into a repository. Use when adopting or refreshing these skills, generating repository-specific Rust rules, or creating validation workflows. Never finalize policy before repository inspection and user approval.
rust-protocol
Engineer and review binary protocols, wire formats, builders, encoders, parsers, framing, stateful messages, bit ordering, integrity, correction, malformed input, and conformance. Use for protocol or serializer code. Do not apply protocol rules to unrelated in-memory models.