refactoring-expert
refactoring-expert 🛠
Keyword: refactoring | Platforms: gemini,claude,codex
High-Performance Refactoring Expert Skill - A fusion of Refactoring Guru's architectural patterns and Supercent's rigorous operational discipline.
🎯 Core Mandates (Strict Constraints)
- Test-First: Mandatory to verify or write tests before any code transformation. No tests = No refactor.
- Behavior Preservation: Absolute prohibition on functional changes. Same input → same output.
- Atomic Steps: One transformation at a time (e.g., Extract Method only). Do not mix refactoring with feature additions or bug fixes.
- Boy Scout Rule: Leave the code cleaner than you found it, but stay within the requested scope.
- Quantitative Constraints:
- Methods: Max 20 lines of code.
- Parameters: Max 3 parameters per method.
- Nesting: Max 2 levels of indentation (if/for/while).
- Complexity: Proactively simplify "Arrow Code."
More from kinhluan/rules-quarkus-skills
quarkus-expert
High-performance Quarkus framework expertise covering reactive patterns, CDI, build-time augmentation, and cloud-native development. Use for general Quarkus questions.
19gradle-expert
Expert knowledge for Gradle Build Tool, dependency management, and Gradle-to-Bazel migration. Use for build configuration and project lifecycle questions.
15vertx-expert
Expert knowledge for Eclipse Vert.x, the reactive engine behind Quarkus. Use for deep reactive programming, Event Loop, and non-blocking I/O questions.
14bazel-expert
Expert knowledge for writing idiomatic Bazel rules, Starlark best practices, and build performance optimization. Use for Bazel build system questions.
9maven-expert
Expert knowledge for Apache Maven, dependency management, BOMs, and Maven-to-Bazel migration. Use for build configuration and project lifecycle questions.
9rules-quarkus
Expert knowledge for building Quarkus applications with Bazel using the rules_quarkus build system. Use when user asks about Quarkus+Bazel builds, augmentation, or troubleshooting.
8