What is ide-refactor?

A refactoring workflow for changing code safely with an editor’s language tools. It saves a workspace checkpoint, applies symbol renames and code changes, runs tests, and can restore the checkpoint if the tests fail.

Use it to rename functions, classes, or variables across a codebase, apply editor-supported code actions, run the resulting tests, and undo a failed refactor.

It reduces the risk of breaking related code during a refactor. The saved checkpoint provides a way back when the change causes problems.

How Oolab-labs/claude-ide-bridge configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Oolab-labs/claude-ide-bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Oolab-labs/claude-ide-bridge/main/.claude/skills/ide-refactor/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-refactor/github.svg)](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-refactor)

Your own site

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-refactor"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-refactor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-refactor"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 797 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.00797
Opus 5.5	$0.00015	$0.00319
Sonnet 5.5	$0.00008	$0.00159
Haiku 4.5	$0.00004	$0.00080

Measured 1mo ago against content hash 71e02de46fe2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ide-refactor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/ide-refactor/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IDE Safe Refactor Workflow

Prerequisites

Check if the getToolCapabilities MCP tool is available to you.
- Not available (no MCP tool by that name): stop and tell the user: "This skill requires the Claude IDE Bridge with a connected VS Code extension. It uses LSP tools (rename symbol, code actions, references, snapshots) that have no CLI equivalent.
  
  To use this skill:
  1. Start the bridge: npm run start-all (in claude-ide-bridge/)
  2. Ensure the Claude IDE Bridge extension is installed in your IDE
  3. Use the claude --ide session (not remote-control)"
- Available: call it. If extensionConnected is false: show the same message. If true: proceed.

Perform refactoring with a safety net. Uses snapshots for instant rollback if tests fail after the change.

Workflow

Phase 1: Checkpoint

Use createSnapshot with name "pre-refactor" to capture current workspace state
Confirm: "Snapshot created. Starting refactoring: $ARGUMENTS"

Phase 2: Plan the refactoring

Analyze what needs to change based on the description: $ARGUMENTS
Use searchWorkspace and getDocumentSymbols to identify all affected symbols
Use findReferences to map the impact across the codebase
Use getCallHierarchy to understand dependency chains
List all files that will be affected and confirm the plan

Phase 3: Execute the refactoring

For symbol renames: 8. Use renameSymbol — this handles all references across the workspace via LSP

For structural changes: 9. Use getCodeActions to check if VS Code has automated refactorings available 10. Use applyCodeAction for supported refactorings (extract method, extract variable, etc.) 11. Use editText for manual structural changes

Phase 4: Clean up

Use organizeImports on every modified file
Use formatDocument on every modified file
Use getDiagnostics to check for new errors introduced by the refactoring

Phase 5: Verify

Use runTests to run the full test suite
If all tests pass:
- Report success with a summary of changes
- The snapshot remains available for manual rollback if needed later
If tests fail:
- Use diffSnapshot with "pre-refactor" to show exactly what changed
- Ask: "Tests failed. Would you like me to roll back?"
- If yes: use restoreSnapshot with "pre-refactor" to instantly revert
- If no: report which tests failed and why, so you can fix manually

Read the full file on GitHub · 84 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 84 lines · 38 tokens per session scan A 71e02de46fe2

Subscribe to this mod's changes

ide-refactor is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (37 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code ai claude developer-tools ide lsp

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

mirrord-operator

Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…

metalbear-co/mirrord · 124 tokens

claude-ide-bridge: Skill for Claude Code