agentmods.dev

claude-ide-bridge: Skill for Claude Code

.claude/skills/ide-refactor/SKILL.md

ide-refactor is a skill for Claude Code from Oolab-labs/claude-ide-bridge. It costs 38 tokens per session (797 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
It reduces the risk of breaking related code during a refactor. The saved checkpoint provides a way back when the change causes problems.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is Oolab-labs/claude-ide-bridge's own configuration. It tells Claude Code how to work on claude-ide-bridge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-ide-bridge configures →

not rated 38repo 4mo ago A scan 38 tokens original MIT
View source ↗ Oolab-labs/claude-ide-bridge
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.

agentmods badge for ide-refactor

README.md
[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-refactor.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.svg" alt="Measured on agentmods" 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00797
Opus 5 $0.00019 $0.00398
Sonnet 5 $0.00008 $0.00159
Haiku 4.5 $0.00004 $0.00080

Measured 8d ago against content hash 71e02de46fe2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 8d 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

  1. 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

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

Phase 2: Plan the refactoring

  1. Analyze what needs to change based on the description: $ARGUMENTS
  2. Use searchWorkspace and getDocumentSymbols to identify all affected symbols
  3. Use findReferences to map the impact across the codebase
  4. Use getCallHierarchy to understand dependency chains
  5. 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

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

Phase 5: Verify

  1. Use runTests to run the full test suite
  2. If all tests pass:
    • Report success with a summary of changes
    • The snapshot remains available for manual rollback if needed later
  3. 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.

  1. 8d 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 (38 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 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 Codeaiclaudedeveloper-toolsidelsp
Related

Other skills, from other repositories

lsp-inspect

Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…

blackwell-systems/agent-lsp · 126 tokens

lsp-refactor

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.

blackwell-systems/agent-lsp · 57 tokens

lsp-understand

Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map.

blackwell-systems/agent-lsp · 0 tokens

lsp-dead-code

Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.

blackwell-systems/agent-lsp · 43 tokens

lsp-safe-edit

Wrap any code edit with before/after diagnostic comparison. Speculatively previews the change first (previewedit), then applies to disk only if the error delta is acceptable. If post-edit errors appear, surfaces code actions for quick fixes. Handles single and multi-file edits.

blackwell-systems/agent-lsp · 59 tokens

lsp-edit-export

Safe workflow for editing exported symbols or public APIs. Use when changing a function signature, modifying a public type, or altering any symbol used outside its own package — finds all callers first so nothing breaks silently.

blackwell-systems/agent-lsp · 46 tokens