rust-2024-migration
Modernize Rust Code for Edition 2024
Rust migrations can be hard when new edition features change style and compiler expectations. This skill helps Claude, Codex, and Claude Code identify Rust 2024 refactoring opportunities and migration steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "rust-2024-migration" from https://skillstore.io/skills/emillindfors-rust-2024-migration.md and its manifest at https://skillstore.io/api/skills/emillindfors-rust-2024-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "rust-2024-migration". A function uses several nested option checks before returning a value.
Expected outcome:
- The skill identifies the nested control flow as a let chain candidate.
- It explains that the change requires Rust 1.88 or later and edition 2024.
- It recommends keeping the original shape if the chain would reduce readability.
Using "rust-2024-migration". A service trait uses async-trait for methods without dynamic dispatch.
Expected outcome:
- The skill suggests native async functions in traits where object safety is not required.
- It warns that boxed dynamic trait objects may still need async-trait.
- It asks the user to confirm public API and minimum compiler support.
Using "rust-2024-migration". A crate is still configured for the 2021 edition.
Expected outcome:
- The skill outlines an edition update checklist.
- It includes cargo fix, compiler version checks, and manual review of modernized patterns.
- It separates mechanical migration steps from optional readability refactors.
Security Audit
SafeAll static findings are false positives caused by Markdown fenced Rust, TOML, and bash examples, not executable Ruby or shell backtick use. The only sensitive-data hit is an example Rust variable named db, not a database file or secret. No prompt injection, exfiltration intent, or unsafe tool use was found in SKILL.md.
Risk Factors
⚙️ External commands (25)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emillindfors-rust-2024-migration/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emillindfors-rust-2024-migration?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emillindfors-rust-2024-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emillindfors-rust-2024-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emillindfors-rust-2024-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
EmilLindfors. (2026). rust-2024-migration security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/emillindfors-rust-2024-migration/audits/4BibTeX citation
@techreport{emillindfors-emillindfors-rust-2024-migration-2026,
author = {EmilLindfors},
title = {rust-2024-migration security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/emillindfors-rust-2024-migration/audits/4},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "rust-2024-migration security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "EmilLindfors"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emillindfors-rust-2024-migration/audits/4"
identifiers:
- type: other
value: "skillstore:emillindfors-rust-2024-migration:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Upgrade a Crate to Rust 2024
Plan edition changes, identify likely refactors, and review minimum compiler requirements before migration.
Simplify Async Rust Code
Find async closures and trait patterns that can use modern Rust syntax with fewer helper crates.
Review Migration Pull Requests
Check whether Rust 2024 refactors are appropriate, readable, and compatible with project constraints.
Try These Prompts
Review this Rust module and list patterns that could use Rust 2024 features. Focus on let chains, async closures, and match ergonomics.
Create a Rust 2024 migration plan for this crate. Include Cargo.toml changes, compiler version concerns, cargo fix steps, and manual review points.
Review these async trait definitions and explain which can use native async fn in traits. Identify any cases that still require async-trait for dynamic dispatch.
Audit this Rust project for Rust 2024 readiness. Prioritize risky changes, public API impact, test gaps, and refactors that should be split into separate commits.
Best Practices
- Verify the project minimum supported Rust version before applying each recommendation.
- Separate edition migration commits from optional style refactors for easier review.
- Run cargo fix, cargo check, and tests after applying Rust 2024 changes.
Avoid
- Do not replace async-trait when dynamic dispatch still requires it.
- Do not apply let chains when they make complex conditions harder to read.
- Do not change the edition without checking downstream users and public API impact.
Frequently Asked Questions
Does this skill modify Rust files automatically?
Which Rust edition does this skill target?
Can it run cargo fix for me?
Does it remove async-trait everywhere?
Is compiler compatibility checked automatically?
Can Claude, Codex, and Claude Code use this skill?
Developer Details
Author
EmilLindforsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
a06681402992ceae98ba04d54cfd4ab004862696
Maintenance freshness
7/18/2026
Usage
4 downloads · 179 views
File structure
📄 SKILL.md