コミット/PR の「全部置換した」「-N%削減」等の完了主張を grep で反証できる残骸や best/typical/worst 試算で検証し、抽出・集約リファクタでは並列度(Promise.all)/fast-path/遅延評価の性能特性退行と、Map/Set 集約キーの cross-kind 衝突による検出漏れも監査する
Use when legacy prompts or older framework flows reference `refactor-cleaner` and you need the modern runtime to resolve that capability cleanly.
Dead code cleanup via pipeline knip + depcheck + ts-prune + javadoc-coverage (multi-language safe removal)
Improves changed code for reuse, simplification, readability, and efficiency without changing behavior, then re-runs tests to prove behavior is unchanged.
Intelligently refactor and improve code quality with incremental, test-backed changes. Use when the user asks to "refactor", "clean up code", "improve code quality",…
Remove code duplication, extract shared patterns, and eliminate type casts and `any` types. Run after implementing new features.
รีแฟกเตอร์และมาตรฐาน Docker project โดยสร้าง docker-compose.yml และ .env file ที่สะอาด ตามแนวทาง best practice มุ่งเน้น structure, consistency และ production readiness ใช้ skill…
For long functions: break into smaller pieces, extract helper functions, reduce nesting, improve testability and readability.
[Code Quality] Removes code duplication and cleans up dead code. Use to eliminate copy-paste code, consolidate similar logic, and remove unused code paths.
Comprehensive refactoring workflow that combines tactical and architectural passes. Runs /refactor (tactical cleanup), /review-arch (architectural restructuring), then /refactor…
Refactor a FastAPI endpoint from monolithic handler to service layer pattern — extract business logic, add error handling, fix DI
During planning after grill-task, decide whether a preparatory refactor step is needed before implementation — runs four parallel A-rule checks.
Model-only playbook for splitting a multi-responsibility class into single-purpose collaborators.
Modernize and improve legacy codebases while maintaining functionality. Use when you need to refactor old code, reduce technical debt, modernize deprecated patterns, or improve…
Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods.
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.
Safe refactoring patterns - extract, rename, restructure with test-driven methodology and dead code detection.
Apply systematic refactoring patterns — strangler fig for legacy migration, seam detection, extract method/class, introduce parameter object, replace conditional with…
Composite: end-to-end refactor with plan, parallel 3-agent implementation, test cleanup, ADR capture, and sync.
Use to plan a behavior-preserving structural improvement — audit the target, ensure test coverage exists, plan small reversible steps, and verify behavior is unchanged.
Kategorizovaný návrh refactoringu (kosmetic / structural / breaking) s per-bucket gates. Generuje proposal dokument, postupně provádí změny po schvalování.
/refactor-rust 커맨드로 실행되는 Rust 코드 리팩토링 스킬. rust-coding-style.md에서 도출된 R-R-01~08 도메인 중심 카탈로그를 기준으로, git worktree 격리 환경에서 코드 냄새를 탐지하고 우선순위 기반 계획을 수립한다.
Use when the goal is to change code structure without changing behavior — this includes extracting a service object from a fat controller or model, splitting a large class,…
[Code Quality] Defines clear boundaries and goals for a refactoring session. Use to establish what WILL and WILL NOT change, set success criteria, and create a focused refactoring…
Acts as a Bash scripting expert that creates and refactors Shell scripts with clean structure, standard conventions, strong error handling, logging, and production-ready — from…
Refactorizar un SKILL.md demasiado largo o mal estructurado extrayendo ejemplos a references/EXAMPLES.md, dividiendo procedimientos compuestos y reorganizando secciones para una…
Get refactoring suggestions with colored diffs. Use when improving code quality. — from satoshistackalotto/skills
Team-based code refactoring with analysis and user-approved changes. Use when: "refactor this code", "リファクタリング", "コード整理", "refactor team", "リファクタチーム".
Proves a behavior-preserving code change (refactor, rename, split, merge, extract, inline, or delete of confirmed-dead code) is actually complete.
Review code for refactorability — surface concrete, prioritized refactoring opportunities grounded in Martin Fowler's smell catalog and SOLID, augmented with static analysis tools…
Get refactoring suggestions with colored diffs. Use when improving code quality. — from satoshistackalotto/skills
Systematic refactoring with small-step discipline. Use when user says 'refactor', 'clean up', 'restructure', 'extract', 'rename', 'simplify', or mentions code smells.
Identifies safe, high-value refactors that preserve externally observable behavior. Use for debt, smells, or “clean this up” asks.
리팩토링 분석 전문가. 기존 코드베이스를 컨벤션 기준으로 분석. Zero-Tolerance 위반 탐지, 영향도 분석, 단계별 리팩토링 계획 수립. /refactor-plan 명령 시 자동 활성화. Serena Memory에 결과 저장.
Catalog of code smells and the matching refactoring techniques that fix them, plus the discipline of refactoring safely (small steps, test-covered, behavior-preserving).
Guidelines for maintaining a clean codebase through limits and abstraction. Use when a file or component becomes difficult to read.
Execute refactoring safely with test-first verification following best practices. Takes refactoring discovery reports as input and performs incremental refactoring with continuous…
SOTA refactoring and modularization principles that LLMs systematically miss. Covers language-agnostic principles plus Rust-specific (visibility, crate boundaries, Cargo features)…
Use when actively refactoring an existing codebase's package or module structure. Detects cycles, oversized modules, misplaced responsibilities, and dependency direction problems,…
Plan a safe, incremental refactor of messy code without changing behavior. Use when code needs restructuring, is hard to change, has grown tangled, or you want to clean it up…
Strukturierte Refactoring-Planung mit Impact-Analyse und schrittweiser Umsetzung für große Codebases.
ACTIVATE for any refactoring, extract, redesign, simplify, or cleanup request across languages. Covers cross-language refactoring principles: trace business flow before…
Expert in improving code structure without changing behavior. Specializes in Design Patterns, SOLID principles, and Anti-Corruption Layers.
Systematic refactoring methodology with safety guarantees for polyglot codebases. TRIGGER when: user asks to refactor code, restructure a module, split a monolith, do a large…
Expert code refactoring specialist for improving code quality without changing behavior. Activate on: refactor, code smell, technical debt, legacy code, cleanup, simplify, extract…
Refactoring techniques for improving code maintainability. Use when refactoring code to reduce complexity and apply SOLID principles.
Fowler's refactoring methodology — loaded by the implementer agent when working with existing code to recognize code smells and apply proven transformations
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off", "fix the design", "Tailwind styling", "color palette" — from…
Refactor code to improve maintainability by consolidating redundant logic and applying DRY principles
Systematischer Prozess für sichere und effektive Refactorings mit Analyse, Planung und Verifikation.
Practical regex patterns across languages and use cases. Use when validating input (email, URL, IP), parsing log lines, extracting data from text, refactoring code with…
Use when a change to an existing system, legacy code, refactor, dependency, data contract, migration, or generated implementation needs regression risk review.
Pin every fixed bug with a test that fails before the fix and passes after, kept beside the code it guards.
Produces grounding context summaries — directory structure, recent diffs, and file patterns — from local repository state, enabling more accurate architectural and implementation…
Review repository changes for regressions and operational risks. Use when validating refactors, install scripts, or environment automation before rollout.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS