improve-code

Automate code quality improvements for Spring Boot Kotlin WebFlux projects.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill improve-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-code
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/eng/spring/skills/improve-code
Command: npx skills add https://github.com/semicolon-devteam/semo --skill improve-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

기존 코드의 품질과 성능을 체계적으로 개선하고, 유지보수를 용이하게 만듭니다.

Core Features & Use Cases

  • 코드 스멜 탐지: 중복, 복잡도, 불필요한 패턴 식별
  • 리팩토링 가이드: 함수 분리, 옵저버 패턴 등 개선 방법 제시
  • 적용 및 검증: 개선 후 lint/compile/test 재검증

Quick Start

코드 스멜을 식별하고 개선 아이템을 제안합니다.

Frequently Asked Questions about improve-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve code quality and performance in Spring Boot Kotlin WebFlux applications?

Code quality improvement in Spring Boot WebFlux projects involves detecting code smells, proposing refactorings aligned with Kotlin and reactive patterns, then validating changes through lint, compilation, and test execution. This Skill automates that full workflow—analysis, planning, implementation, and rollback—to systematically enhance maintainability and performance.

What code smells and anti-patterns can be detected in Kotlin codebases?

Code smell detection identifies duplicate logic, cyclomatic complexity violations, unnecessary patterns, and non-idiomatic Kotlin constructs. The Skill flags these issues and recommends concrete refactorings—such as function extraction and observer pattern application—tailored to Spring Boot and reactive design principles.

How does ktlint integration enforce code quality standards in refactoring?

ktlint enforcement validates that proposed refactorings comply with Kotlin style guidelines. After changes are applied, the Skill runs ktlint checks alongside Gradle compilation and test suites to verify that code quality improvements don't introduce style violations or functional regressions.

Can I automate refactoring validation across Kotlin Spring Boot projects?

Yes. The Skill automates the complete validation cycle—lint checks, compilation, and test execution—after each refactoring is applied. It generates verification reports and SEMO messages so you can confirm that improvements are safe and maintain project integrity.

What happens if a code quality improvement breaks existing functionality?

The Skill includes rollback workflows to revert unsafe changes. If validation tests fail or regressions are detected during lint, compile, or test phases, you can safely undo the refactoring and return to the prior state without manual recovery.