菜单
Dependency lock and Cargo.lock conflict policy for Rust workspaces. Covers when to update, when to regenerate, manual conflict handling, and merge/sync guidelines to prevent recurring Cargo.lock merge conflicts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cargo-lock-policy |
| description | Dependency lock and Cargo.lock conflict policy for Rust workspaces. Covers when to update, when to regenerate, manual conflict handling, and merge/sync guidelines to prevent recurring Cargo.lock merge conflicts. |
| source | auto-skill |
| extracted_at | 2026-06-22T02:23:54.746Z |
Cargo.lock 要纳入 git 版本控制，放在 workspace root。它的作用是锁定可复现构建，因此任何会导致依赖树变化的变更，都应同步更新 lock 文件。
Cargo.toml（增/删/升级依赖，改 features）Cargo.toml 中的 reqwest、pyo3、rusqlite 等主要 cratecargo update、cargo upgrade 后在修改完 Cargo.toml 后，执行：
cargo update --workspace
cargo check --workspace
cargo test --workspace
cargo update --workspace 后确认缓存正常，再提交 Cargo.lockcargo metadata --lockfile-version 或等价 gated check）不要对 main 做 git rebase 与远端强制同步。正确做法：
git fetch origingit log --oneline origin/main..HEAD）git merge origin/main --no-commit --no-ffCargo.toml：手工抉择应保留的版本（通常跟随 changelog / commit 意图）Cargo.lock：取较新那份完全有效的 lock，或者用 cargo update --workspace 一次性重新生成，再 git add Cargo.lockgit commit 完成后，再 push| 情况 | 处理 |
|---|---|
| 仅有 format change | 保留当前工作树 + checkout 的 Cargo.lock |
| 仅有 version bump | 保留较新锁文件；re-run cargo update 再提交 |
| 大量依赖 inserted/removed | 删除冲突部分，用 cargo update --workspace 重新生成 |
| 不确定哪边正确 | 跑 cargo tree / cargo metadata 验证后再提交 |
cargo check 通过再 commitCargo.lock 时必须同时 commit 对应 Cargo.toml.gitignore 不要把 Cargo.lock 放进去git checkout --ours Cargo.lock 或 --theirscargo update --workspacegit add Cargo.lock && git commit先确定最终依赖方案（锁定版本、feature flags），然后：
cargo update -p <crate_name>
再在 Cargo.toml 和 Cargo.lock 同时确认提交。
Cargo.lockCargo.lock 仅包含 workspace 的依赖集合，不需要 flush--force merge main：强制同步必须走 merge + 手工冲突解决Systematic pre-merge verification workflow for Rust monorepo branches. Check compilation, tests, clippy, grep leftovers, then fix → commit → push → PR. Use when user says "check work done in this branch" or before merging any PR.
Audit and fix documentation (README, ARCHITECTURE, CHANGELOG) against current codebase while waiting for CI/bot reviews on a PR. Fix factual drift, dead references, and add changelog entries — then commit docs to the same branch.
Daytona sandbox knowledge for answering user questions about remote development environments. Use when the user asks about Daytona, sandboxes, remote execution, cross-platform builds, or needs to run code on cloud infrastructure instead of locally. Provides API details, pricing, troubleshooting, and CLI commands.
Modal.com knowledge for answering user questions about serverless GPU compute, cost comparison with Daytona, and Python-based sandbox workflows. Use when the user asks about GPU access, ML training, Modal pricing, serverless sandboxes, or wants to compare cloud compute options for their Rust/Python projects.
Mandatory project quality workflow for the specgen Rust monorepo. Enforces zero-warning policy, formatting standards, and test compliance. Trigger before any commit, pull request, or completion of a coding task. Also trigger when the user says "check quality", "run QA", or "is it ready?".
Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work. Trigger on first run in any new codebase, after AI-assisted coding sessions, or when user says "clean up", "review quality", "check slop", or "anti-slop".