refactor
Find dead code, duplications, complexity issues, and refactoring opportunities. Use when cleaning up code, removing unused exports, simplifying complex functions, or during tech debt sprints.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Refactor & Dead Code Removal
Analyze and refactor code for clarity, maintainability, and removal of unused code.
Scope
1. Dead Code Detection
- Unused exports (functions, types, constants)
- Unused imports
- Unreachable code paths
- Commented-out code blocks
- Unused CSS classes
- Deprecated code marked for removal
- Unused dependencies in package.json
2. Code Duplication
- Repeated logic across files (DRY violations)
- Similar components that should be abstracted
- Copy-pasted utility functions
- Duplicated type definitions
3. Complexity Reduction
- Functions exceeding 50 lines
- Deeply nested conditionals (>3 levels)
- Complex boolean expressions
- God components doing too much
- Files approaching 300 lines (per AGENTS.md)
4. Naming & Clarity
- Unclear variable/function names
- Misleading names that don't match behavior
- Inconsistent naming conventions
- Magic numbers without constants
5. Pattern Consistency
- Inconsistent error handling patterns
- Mixed async patterns (callbacks vs promises vs async/await)
- Inconsistent state management approaches
- Varying component structure patterns
6. Type Safety
-
anytypes that should be specific - Missing type annotations
- Overly broad types that could be narrowed
- Type assertions that could be avoided
Output Format
For each finding:
[TYPE: DEAD_CODE|DUPLICATION|COMPLEXITY|NAMING|PATTERN|TYPES]
File: path/to/file.ts:lineNumber
Issue: Brief description
Current: Code snippet or pattern
Recommended: Refactored approach
Risk: LOW|MEDIUM|HIGH (breaking change potential)
Actions
- Run
npm run lintto catch obvious issues - Run
npm run type-checkfor type issues - Search for unused exports with grep patterns
- Identify files over 300 lines
- Look for duplicated code blocks
Refactoring Principles
Per AGENTS.md guidelines:
- Single Responsibility Principle
- Reuse > Rebuild
- Abstract only when pattern appears 3+ times
- Keep PRs scoped to single purpose
Post-Review
Generate:
- Safe deletions (no breaking changes)
- Refactoring candidates with dependency analysis
- Suggested extraction of shared utilities
- Migration path for larger refactors
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!