Menu
Refactor outdated patterns in the codebase based on user input
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review code changes from a specific angle or do a general pass. Use when the user wants a code review of their current branch or specific changes. For a thorough review covering all checks, use the @agent-review subagent instead. To review changes against a spec/source of truth (with doc-coverage and duplication checks), use /scoped-review instead.
Scoped code review — determines the change scope (explicit, discussion, or git), picks a source of truth (discussion, new docs, or code), then reviews the changes for correctness, doc agreement, doc coverage, convention adherence, duplicated shapes that want a shared abstraction, hand-rolled complex logic that wants a named/shared function, and unit-test coverage of complex logic.
Create a git commit with a well-crafted message. Use proactively whenever the user asks to commit changes or amend a commit.
Review documentation for accuracy against the current implementation. Use when documentation files are modified, when code changes may have made docs outdated, or when the user asks about documentation accuracy.
Refactor frontend components to follow Mantine coding conventions. Use when asked to refactor, modernize, or clean up UI code.
| name | refactor |
| description | Refactor outdated patterns in the codebase based on user input |
| argument-hint | <pattern to refactor, e.g. "Bacon.js to Zustand" or "any types to proper types"> |
| disable-model-invocation | true |
Systematically find and convert all instances of the outdated pattern described above.
Understand the target: Parse the refactoring description to identify the old pattern and the desired new pattern.
Survey the codebase: Search for all instances of the old pattern. Use grep/glob to find every occurrence. Report the full scope before making changes:
Plan the approach: Present a migration plan:
Get approval: Show the plan and ask the user to confirm scope before proceeding. The user may want to do it all at once or in batches.
Execute: For each file:
Verify: After all changes, run bun lint to catch type errors and lint issues.
Fix any issues introduced by the refactoring.
For frontend/UI refactoring, prefer the /refactor-frontend skill which reads the
full coding conventions from src/client/coding-conventions.md.
These are known legacy patterns in this codebase:
any types: Replace any with proper TypeScript types.$/param/ parameterization.bun lint after each batch of changes to catch issues early.