rust-code-change

仓库创建 2026年6月24日最近提交 22 天前SkillHot 收录 22 天前
▸ 精选理由

专注 Rust 特性的变更规范,适合库/系统级开发者。

这个 Skill 做什么

在修改 Rust 代码或 crate 时保持所有权、错误与公共 API 的边界与合同。

改 Rust 代码的时候,它帮你把所有权、错误处理和对外 API 的边界搞清楚,避免只是为了过 borrow checker 而做出含糊的改动。只要改源码、Cargo 元数据、feature、trait、async/unsafe、MSRV、toolchain 或公开 crate 接口时就需要用。特别之处是把语义合同和所有权关系当成一等公民,优先保证接口与错误契约明确,而不是单纯消除编译报错。

▸ 展开 SKILL.md 英文原文

Apply this skill when Rust source, Cargo metadata, features, traits, errors, ownership, async runtime, unsafe code, tests, examples, benchmarks, release profiles, MSRV, toolchain declarations, standard-library APIs, or public crate APIs are created or changed. Use when this capability is needed.

开发编程Rust所有权API稳定通用
0
Stars
0
Forks
40
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/tomevault-io/skills-registry/main/0disoft--mustflow--rust-code-change/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/tomevault-io/skills-registry/main/0disoft--mustflow--rust-code-change/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Rust Code Change

<!-- mustflow-section: purpose -->
## Purpose

Preserve Rust ownership, error, trait, feature, async runtime, unsafe, and public crate boundaries while making a focused change. A Rust change is successful only when it clarifies ownership and contracts, not when it merely silences the borrow checker.

Rust's compiler feedback can be especially useful for AI-assisted work because it rejects many
invalid states with concrete errors. That benefit has a real cost: compile time, target-directory
growth, native toolchain setup, release-profile slowness, and smoke-target selection must be managed
instead of treated as incidental.

<!-- mustflow-section: use-when -->
## Use When

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有