'code-smells' 검색 결과

Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review touched code for maintainability smells such as duplication, awkward indirection, suspicious clones, dead code, poor naming, and Boy Scout cleanup opportunities. Use when a broad review needs a dedicated maintainability pass or when the user asks for code-smell review specifically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

需要在不修改业务代码的前提下诊断既有前端代码的结构性可维护性问题，并要求提供证据、误判检查与候选重构方向时。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when diagnosing structural maintainability problems in existing frontend code before deciding how to refactor it, especially when evidence, false-positive checks, and candidate transformations are needed without editing business code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects code smells in PHP codebases. Identifies God Class, Feature Envy, Data Clumps, Long Parameter List, Long Method, Primitive Obsession, Message Chains, Inappropriate Intimacy. Generates actionable reports with refactoring recommendations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects C# code smells during review. Anti-patterns, async misuse, DI mistakes, fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.