Find matching identifiers, strings, properties, and JSX references. The scan includes Vue template interpolations and directive expressions.

ripide scan useStore
ripide scan useStore --kind identifier-reference,import-specifier
ripide scan useStore --graph mermaid

--graph mermaid|dot draws relative import/export edges between hit files for quick triage.

Rename references using the native TypeScript 7 language server, including imports, JSX, types, and aliases. Property keys change only when they refer to the same symbol.

# Preview the changes
ripide rename useStore useAppStore

# Write changes after type checking
ripide rename useStore useAppStore --apply

# Ambiguous declarations? Pick one or rename all
ripide rename useStore useAppStore --scope src/store.ts --apply
ripide rename useStore useAppStore --all --apply

Imports and references change together. The unrelated string keeps its spelling:

# src/store.ts
-export function useStore() { return 1 }
+export function useAppStore() { return 1 }
# src/consumer.ts
-import { useStore } from './store.js'
-export const value = useStore()
+import { useAppStore } from './store.js'
+export const value = useAppStore()
 export const label = 'useStore'

Replace an imported binding with a project export, such as replacing eventHandler(...) with defineAdminApiHandler(...). RipIDE updates references and imports, then removes the old import. It preserves the call arguments and function body.

New imports preserve the replaced relative import's extension policy. For package imports, they follow relative imports in the consumer, then nearby project files. Without a local policy, they use extensionless paths. JavaScript paths keep emitted .js, .mjs, or .cjs endings for TypeScript targets. Review mixed import policies in the dry run before applying.

ripide replace eventHandler defineAdminApiHandler
ripide replace eventHandler defineAdminApiHandler --apply

# Ambiguous target exports? Pick the declaring file
ripide replace eventHandler defineAdminApiHandler --target-scope layers/admin/server/utils/admin-api.ts --apply

# Route an existing binding through a named barrel and a framework alias
ripide replace getSiteConfig getSiteConfig --target-scope ../nuxt-site-config/src/runtime/server/index.ts --target-import '#site-config/server' --apply

--target-scope can select a named re-export barrel outside the consumer project. --target-import sets its import path explicitly, including Nuxt aliases. Value and type exports retain their import kind. Existing imports from that path merge safely. Default discovery still selects direct declarations and keeps the relative import policy.

Run nuxi prepare first to generate Nuxt's type declarations. RipIDE uses these files to resolve auto-imported composables, utilities, and components used in pages and other consumers. If a move requires an explicit import in a Vue file without a script block, RipIDE refuses it.

# A composable used in pages with no explicit import
ripide rename useCounter useTally --tsconfig .nuxt/tsconfig.json --apply

# Moving out of utils/composables/components adds explicit imports to consumers
ripide move format --from utils/format.ts --to lib/format.ts --apply

Move a top-level export and update its imports. RipIDE splits declarations such as export const a = 1, b = 2 and preserves aliases. It copies required imports and removes unused ones. If the symbol depends on a local, unexported helper, it refuses the move.

ripide move helper --from src/utils/a.ts --to src/utils/helpers.ts --apply

Update import paths when moving or renaming a file. The Vue adapter also updates component tags in PascalCase and kebab-case.

ripide rename-file src/utils.ts src/lib/helpers.ts --apply

Delete a top-level declaration after checking for references, then remove imports used only by that declaration. If references remain, RipIDE prints their locations and refuses the deletion. Omit --apply to preview the changes.

ripide delete helper --from src/utils.ts
ripide delete helper --from src/utils.ts --apply

Rename class tokens in string literals, Vue class and :class attributes, and CSS @apply directives. RipIDE preserves variant prefixes (hover:, dark:md:), ! important markers, and arbitrary values.

# Single pair
ripide css-class-rename bg-gray-500 bg-neutral-500 --apply

# Bulk design-token migration
ripide css-class-rename --map tokens.json --apply

# Seed the map by listing every class in the repo
ripide css-class-scan --json > tokens.raw.json

# Find barely used classes to clean up
ripide css-class-scan --sort count-asc

# Find files introducing the most unique class tokens
ripide css-class-scan --by file

List declarations by file. Use --exports exported for exports or --exports local for declarations without exports.

ripide tree --exports exported
ripide tree --exports local --glob '*.ts'

In agent environments (std-env's isAgent), defaults to a compact architecture summary.

Report top-level declarations with no semantic project references. Review each result before deleting it. External callers, frameworks, dynamic registries, and entrypoints may still use these declarations.

ripide unused
ripide unused --exports local
ripide unused --exports all --json

--json emits the same contract in terminals and detected agent environments. The default JSON profile is compact. Use --profile full for complete source content. Every response contains _tag, command, base, and data. Mutation tags are Preview, Applied, Refused, or Empty. Discovery uses Result; failures use Error. For mutating commands, compact JSON returns [path, lines] tuples inside data instead of full source files. If line ranges shift, tuples include both ranges: [path, beforeLines, afterLines]. Lines are one-based and inclusive. "3,10-12" identifies separate ranges; "3+" marks a gap after line 3. File moves appear separately as moves: [[from, to]]. The _tag identifies the outcome. The data.verification field reports checks. Empty warnings and regressions are omitted. Verification entries use [checker, scope, files, newErrors]. An optional fifth number counts errors excluded from the result. Skipped checks return "disabled", "no-changes", or "not-applicable". After applying, earlier file reads are outdated. Read changed ranges only when you need current code. If an editing tool requires a fresh read, follow that requirement. Use --profile full --json for complete before/after content. If verification finds new type errors, the command refuses --apply and exits with a non-zero status.

ripide rename useStore useAppStore --apply --profile agent --json
# {
#   "_tag": "Applied", "command": "rename", "base": "/project",
#   "data": {
#     "changes": [["src/store.ts", "12"], ["src/app.ts", "1,8"]],
#     "verification": [["typescript", "touched", 2, 0]]
#   }
# }