Skip to content
Skill

Migrate to rust

Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a mode

Install
Scripts
Python
Platforms
Claude Code, Codex, Cursor
GitHub stars
24.4K
Last commit
today
License
Apache-2.0
Listing updated
today

When your agent uses it

Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure/fix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 4 files (132 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/migrate-to-rust to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/migrate-to-rust &&
cp -R "$tmp/skills/developers/migrate-to-rust" ~/.claude/skills/migrate-to-rust &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/migrate-to-rust inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/migrate-to-rust to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/migrate-to-rust &&
cp -R "$tmp/skills/developers/migrate-to-rust" ~/.agents/skills/migrate-to-rust &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/migrate-to-rust inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/migrate-to-rust to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/migrate-to-rust &&
cp -R "$tmp/skills/developers/migrate-to-rust" ~/.cursor/skills/migrate-to-rust &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/migrate-to-rust inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/google/skills.git --path skills/developers/migrate-to-rust

Or copy the folder to ~/.gemini/skills/migrate-to-rust yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/migrate-to-rust:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/migrate-to-rust &&
cp -R "$tmp/skills/developers/migrate-to-rust" ~/.copilot/skills/migrate-to-rust &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/migrate-to-rust inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/google/skills.git

Then copy skills/skills/developers/migrate-to-rust into your agent's skills folder as migrate-to-rust. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Migrate to rust FAQ

How do I install Migrate to rust in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/migrate-to-rust to use it in all your projects, or to .claude/skills/migrate-to-rust in one project.

Does Migrate to rust run scripts?

Yes. It runs Python scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Migrate to rust?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Migrate to rust?

The closest alternatives to Migrate to rust are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Make repo contribution.

More from google/skills

  1. Google platform decision and setup guidance, loaded on demand from Google's skill catalog

    • Open source
    • 24.4K GitHub stars
  2. Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services an

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  3. Provides expert guidance on Identity and Access Management (IAM) and authenticating and authorizing to Google Cloud services and APIs, cover

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  4. Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resour

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  5. Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter,

    • Open source
    • 24.4K GitHub stars
  6. Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its

    • Open source
    • 24.4K GitHub stars

Alternatives to Migrate to rust

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools