Borrowing it
Nothing to install: this file belongs to mizchi/lsmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mizchi/lsmcp/main/.claude/commands/refactor.mdgit clone --depth 1 https://github.com/mizchi/lsmcpWrote 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.
[](https://agentmods.dev/commands/mizchi/lsmcp/refactor)<a href="https://agentmods.dev/commands/mizchi/lsmcp/refactor"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/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.
<a href="https://agentmods.dev/commands/mizchi/lsmcp/refactor"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00610 |
| Opus 5.5 | $0.00000 | $0.00244 |
| Sonnet 5.5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Command
When I need to refactor TypeScript code in this project, follow these steps:
1. Analyze Current Code Structure
- Use
mcp__typescript__get_module_symbolsto understand module exports - Use
mcp__typescript__get_type_at_symbolto analyze type information - Use
mcp__typescript__find_referencesto find all usages before refactoring
2. Choose Appropriate Refactoring Tools
For Symbol Operations
- Rename: Use
mcp__typescript__rename_symbolinstead of Edit/MultiEdit - Delete: Use
mcp__typescript__delete_symbolto remove symbols and their references - Find usages: Use
mcp__typescript__find_referencesinstead of grep
For File Operations
- Move file: Use
mcp__typescript__move_fileinstead of bash mv - Move directory: Use
mcp__typescript__move_directoryfor entire directories
For Type Analysis
- Get type info: Use
mcp__typescript__get_type_at_symbol - Module analysis: Use
mcp__typescript__get_module_symbols - Scope analysis: Use
mcp__typescript__get_symbols_in_scope
3. Verify Changes
After refactoring:
- Run
pnpm typecheckto ensure no TypeScript errors - Run
pnpm lintto check code style - Run
pnpm testto verify functionality - Use
mcp__typescript__get_diagnosticsto check for issues
4. Common Refactoring Patterns
Extract Interface/Type
- Identify the type structure using
get_type_at_symbol - Create new type definition file
- Use
rename_symbolto update references
Move Module
- Use
move_fileormove_directory - Tool automatically updates all imports
- Verify with
get_diagnostics
Rename Across Project
- Use
find_referencesto see impact - Use
rename_symbolfor safe renaming - Check affected files with
git status
5. Best Practices
- Always use TypeScript MCP tools for semantic operations
- Never use text-based Edit/MultiEdit for refactoring
- Check references before deleting or moving
- Run tests after each refactoring step
- Commit frequently with descriptive messages
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 · 66 lines · 0 tokens per session scan A 5c6d2514a800
refactor is a command published in the GitHub repository mizchi/lsmcp (454 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 tokens. 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.
Other commands, from other repositories
devkit.typescript.code-review
Provides comprehensive TypeScript monorepo code review for Nx workspaces including NestJS backend, React web, and React Native mobile apps. Use when reviewing architecture, boundaries, security, performance, CI/CD and Nx-specific practices.
review-typescript
Audit a codebase for type-system erosion and write a markdown report. TRIGGER WHEN: the user asks to review TypeScript for type safety, any leakage, unsound casts, tsconfig strictness, exhaustiveness, generics soundness, or missing runtime validation at boundaries. DO NOT TRIGGER WHEN: style review (use…
harness:naming-craft
LLM-judgment skill that critiques identifier names (variables, functions, types, files) against a curated rubric catalog seeded from Martin / Beck / Karlton. First craft-pipeline ceiling skill; cross-cutting (other craft skills call into it for domain-specific naming).
finn
Invoke Finn, your Senior Frontend Developer for React, Next.js, React Native, TypeScript, and TailwindCSS implementation.
review-as-pocock
Fix this TypeScript code as if you were Matt Pocock: eliminate unsafe patterns, preserve inference, and rewrite with modern type-safety best practices (satisfies, generics, discriminated unions, type predicates), showing patch-ready fixes with brief explanations.
ts-review
Comprehensive TypeScript code review with type safety, performance, and best practices analysis.