Agent skill

Rust Analyzer Ssr

Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace.

Apache-2.0Auto-check passedDevelopment

Install Rust Analyzer Ssr

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .claude/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .claude/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .agents/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .agents/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .cursor/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .cursor/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rocky-data/rocky.git --path engine/.claude/skills/rust-analyzer-ssr

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .gemini/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .gemini/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .github/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .github/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .github/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rocky-data/rocky rust-analyzer-ssr --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rocky-data/rocky.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engine/.claude/skills/rust-analyzer-ssr .opencode/skills/rust-analyzer-ssr && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rust-analyzer-ssr" agent skill from https://github.com/rocky-data/rocky/tree/main/engine/.claude/skills/rust-analyzer-ssr into .opencode/skills/rust-analyzer-ssr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rust-analyzer-ssr", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: rust-analyzer-ssr
GitHub stars: 304
Token cost: ~1.4k tokens
SKILL.md length: 504 words
Files: 1
Skills in repo: 22
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace.

Tasks that involve Refactoring
SKILL.md covers When to Use, Basic Syntax, Common Patterns and Constraints, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rust Analyzer Ssr is an agent skill from rocky-data/rocky. Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace. Apply when refactoring API shapes, migrating patterns, or searching for code structure across the workspace crates.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. It works with Rust. The repository describes itself as: A SQL transformation engine that type-checks your whole pipeline and catches breaking changes before they run — branches, replay, column-level lineage, compile-time contracts… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Refactoring

Example prompts

“/rust-analyzer-ssr”

What it can do on your machine

Read from SKILL.md and the folder at commit 46be77e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are rust, json and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- gist.github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rust Analyzer Ssr loads about 1.4k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 504 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rocky-data/rocky at commit 46be77e, republished under its Apache-2.0 licence (© rocky-data). 504 words, ~1,447 tokens.

Download SKILL.mdSave it as .claude/skills/rust-analyzer-ssr/SKILL.md (or your agent's skills folder).

name: rust-analyzer-ssr
description: Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace. Apply when refactoring API shapes, migrating patterns, or searching for code structure across the workspace crates.

rust-analyzer Structural Search and Replace (SSR)

Source: vendored from davidbarsky/8fae6dc45c294297db582378284bd1f2 @ 191b2ee46088920de97d682561e2abd1edd64a42 (SKILL-3.md). Author: David Barsky (rust-analyzer contributor at Meta). This is a pure tooling reference with no style opinions.

Use rust-analyzer's SSR for semantic code transformations in Rust projects. SSR matches code by AST structure and semantic meaning, not text. In Rocky this is especially useful for cross-crate refactors against the multi-crate workspace — string grep regularly over-matches.

When to Use

Refactoring patterns across a codebase (rename, restructure, migrate APIs)
Converting between equivalent forms (UFCS to method calls, struct literals to constructors)
Finding all usages of a specific code pattern
Semantic-aware search that understands type resolution

Basic Syntax

<search_pattern> ==>> <replacement_pattern>

Placeholders capture matched code:

$name — matches any expression/type/pattern in that position
${name:constraint} — matches with constraints

Common Patterns

Swap function arguments

foo($a, $b) ==>> foo($b, $a)

Convert struct literal to constructor

Foo { a: $a, b: $b } ==>> Foo::new($a, $b)

UFCS to method call

Foo::method($receiver, $arg) ==>> $receiver.method($arg)

Method to UFCS

$receiver.method($arg) ==>> Foo::method($receiver, $arg)

Wrap in Result

Option<$t> ==>> Result<$t, Error>

Unwrap to expect

$e.unwrap() ==>> $e.expect("TODO")

Match only literals

Some(${a:kind(literal)}) ==>> ...

Match non-literals

Some(${a:not(kind(literal))}) ==>> ...

Constraints

Constraint	Matches
`kind(literal)`	Literal values: `42`, `"foo"`, `true`
`not(...)`	Negates inner constraint

How to Invoke

Via Comment Assist (Interactive)

Write a comment containing an SSR rule, then trigger code actions:

rust

// foo($a, $b) ==>> bar($b, $a)

Actions appear: "Apply SSR in file" or "Apply SSR in workspace"

Via LSP Command

json

{
  "command": "rust-analyzer.ssr",
  "arguments": [{
    "query": "foo($a) ==>> bar($a)",
    "parseOnly": false
  }]
}

Via CLI

bash

rust-analyzer ssr 'foo($a, $b) ==>> bar($b, $a)'

Key Behaviors

Path Resolution: Paths match semantically. foo::Bar matches Bar if imported from foo.

Auto-qualification: Replacement paths are qualified appropriately for each insertion site.

Parenthesization: Automatic parens added when needed (e.g., $a + $b becoming ($a + $b).method()).

Comment Preservation: Comments within matched ranges are preserved.

Macro Handling

SSR can match code inside macro expansions, but with an important restriction: all matched tokens must originate from the same source.

Example: Macro Boundary

rust

macro_rules! my_macro {
    ($x:expr) => {
        foo($x, 42)  // "42" comes from macro definition
    };
}

my_macro!(bar);  // "bar" comes from call site

The expanded code is foo(bar, 42). Here:

bar originates from the call site (what the user wrote)
foo, 42 originate from the macro definition

If you search for foo($a, $b):

It would NOT match the expanded foo(bar, 42) because $a would capture bar (call site) but $b would capture 42 (definition site) — these cross the macro boundary.

Show full SKILL.md (180 more words)Show less

Why This Limitation Exists

SSR can only generate edits for code the user actually wrote. If a match spans both user code and macro-generated code, SSR couldn't produce a valid edit — it would need to modify the macro definition, which is a different (and potentially shared) piece of code.

What SSR CAN Do With Macros

Match code entirely within macro arguments: my_macro!(foo($a)) can match foo($a)
Match the macro call itself: my_macro!($x) works
Match expanded code where all tokens come from call-site arguments

Other Limitations

Constraints limited to kind(literal) and not()
Single-identifier patterns (foo ==>> bar) may be filtered if ambiguous
Cannot modify use declarations with braces

More Examples

Convert Option methods

$o.map_or(None, Some) ==>> $o

Change field access

$s.foo ==>> $s.bar

Reorder struct fields

Foo { a: $a, b: $b } ==>> Foo { b: $b, a: $a }

Generic type transformation

Vec<$t> ==>> SmallVec<[$t; 4]>

Source Files

Core implementation: crates/ide-ssr/src/ (in the rust-analyzer repo)
IDE integration: crates/ide/src/ssr.rs (in the rust-analyzer repo)
Tests with examples: crates/ide-ssr/src/tests.rs (in the rust-analyzer repo)

Rocky-specific examples

Cross-crate patterns you might want to run against the Rocky workspace:

# Find every place a SQL identifier is interpolated without validation
format!($fmt, $ident) ==>> /* audit: should go through rocky_sql::validation */

# Migrate an adapter trait method
Adapter::old_method($self, $arg) ==>> $self.new_method($arg)

# Swap the ordering of a tagged payload
RunOutput { tables_copied: $t, materializations: $m, ..$rest } ==>> RunOutput { materializations: $m, tables_copied: $t, ..$rest }

Always dry-run with parseOnly: true or preview in the editor before applying workspace-wide — the multi-crate workspace makes a botched refactor expensive to back out.

Files

Just SKILL.md in engine/.claude/skills/rust-analyzer-ssr of rocky-data/rocky.

Open the folder on GitHubat commit 46be77e

Compare with similar skills

Rust Analyzer Ssr next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rust Analyzer Ssr compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rust Analyzer Ssr this skillrocky-data/rocky	304	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Migrate Core Code to Submodulestinyhumansai/openhuman	42k	—	~2.6k	Automated safety check: Pass	GPL-3.0	today
Rust Best Practicesfarm-fe/farm	5.6k	3 repos	~1.1k	Automated safety check: Pass	MIT	16 days ago
RTK Rust Design Patternsrtk-ai/rtk	83k	—	~1.9k	Automated safety check: Pass	Apache-2.0	today
RTK Rust Code Simplifierrtk-ai/rtk	83k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Rust Hygiene Audittsz-org/tsz	577	—	~1.5k	Automated safety check: Pass	Apache-2.0	28 days ago

Similar skills

Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
42k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
5.6k GitHub starsUsed in 3 repos~1.1k tokens
DevelopmentAuto-check passed
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
83k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
RTK Rust Code Simplifier
rtk-ai/rtk
Reviews RTK's Rust code for over-engineering and verbose patterns, applying idioms like iterator chains and early returns while protecting a specific list of constraints from being simplified away.
83k GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
Rust Hygiene Audit
tsz-org/tsz
Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.
577 GitHub stars~1.5k tokensUpdated 28 days ago
DevelopmentAuto-check passed
Coding Agent
mastra-ai/mastra
Authoring playbook for building agents that write, edit, review, or refactor code.
29k GitHub stars~2.3k tokensUpdated today
DevelopmentAuto-check passed

Questions about Rust Analyzer Ssr

What does Rust Analyzer Ssr do?

Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace. Rust Analyzer Ssr is an agent skill from rocky-data/rocky. Use rust-analyzer's Structural Search and Replace (SSR) for semantic Rust code transformations across the engine workspace.

When should I use Rust Analyzer Ssr?

Rust Analyzer Ssr fits situations like: tasks that involve Refactoring.

How do I install Rust Analyzer Ssr in Claude Code?

Run `npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a claude-code`. Or copy the skill folder (engine/.claude/skills/rust-analyzer-ssr in rocky-data/rocky) into .claude/skills/rust-analyzer-ssr in your project. Claude Code loads it when a task matches its description.

How do I install Rust Analyzer Ssr in Codex?

Run `npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a codex`. Or copy the skill folder (engine/.claude/skills/rust-analyzer-ssr in rocky-data/rocky) into .agents/skills/rust-analyzer-ssr in your project. Codex loads it when a task matches its description.

Can I use Rust Analyzer Ssr in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rocky-data/rocky --skill rust-analyzer-ssr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-analyzer-ssr, .gemini/skills/rust-analyzer-ssr, .github/skills/rust-analyzer-ssr and .opencode/skills/rust-analyzer-ssr in your project.

What does Rust Analyzer Ssr need to run?

SKILL.md names no scripts, command-line tools or credentials: Rust Analyzer Ssr is instructions for the agent only.

Does Rust Analyzer Ssr access the network?

SKILL.md names 1 domain. As links in the text: gist.github.com. This is read from the text; nothing was executed.

Is Rust Analyzer Ssr safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rust Analyzer Ssr use?

Rust Analyzer Ssr is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rust Analyzer Ssr use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rust Analyzer Ssr?

Skills that share tags, products or a category with Rust Analyzer Ssr: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and RTK Rust Code Simplifier (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rust Analyzer Ssr?

rocky-data (a GitHub organization) maintains it in rocky-data/rocky, which has 304 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

Source: rocky-data/rocky on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Rust Analyzer Ssr

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

rust-analyzer Structural Search and Replace (SSR)

When to Use

Basic Syntax

Common Patterns

Swap function arguments

Convert struct literal to constructor

UFCS to method call

Method to UFCS

Wrap in Result

Unwrap to expect

Match only literals

Match non-literals

Constraints

How to Invoke

Via Comment Assist (Interactive)

Via LSP Command

Via CLI

Key Behaviors

Macro Handling

Example: Macro Boundary

Why This Limitation Exists

What SSR CAN Do With Macros

Other Limitations

More Examples

Convert Option methods

Change field access

Reorder struct fields

Generic type transformation

Source Files

Rocky-specific examples

Files

Compare with similar skills

Similar skills

More from rocky-data/rocky

Related

Questions about Rust Analyzer Ssr