'refactor' 검색 결과

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).

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

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation fits a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code-quality foundations, see clean-code. For managing complexity, see software-design-philosophy.

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

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

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

AI DevKit · Systematic structural or multi-file refactors across any stack while preserving behavior and public contracts. Use for reorganizing modules, boundaries, naming, APIs/contracts, staged refactor plans, or refactor risk review.

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

Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.

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

Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what should we fix first?", or "how do I justify refactoring to management?". Do NOT trigger for: server health checks, HTTP /health endpoints, Kubernetes probes, database health, or application uptime — "health" in those contexts is infrastructure, not code quality. Also not for single-function refactoring questions.

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

Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring. Use when improving code quality through structured refactoring passes.

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

Start a complete plugin refactoring workflow that analyzes plugin structure, creates a refactoring plan with tasks, and guides through execution. Use when you need to refactor an entire plugin — triggers assessment, design, planning, and parallel agent execution phases.

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

Use this skill when architecting new Claude Code agents following Anthropic best practices. Guides through YAML frontmatter creation, agent structure definition, role boundaries, and validation. Critical for creating minimal agent files (~150 lines) with proper skill invocations. Examples: <example>Context: User wants to create a new agent for security auditing user: "Create a security-auditor agent" assistant: "I'll use the agent-creator skill to build this agent following Anthropic best practices" <commentary>New agent creation requires the agent-creator skill to ensure proper structure and YAML frontmatter.</commentary></example> <example>Context: Existing agent file is too verbose and needs refactoring user: "The architect agent is 2000 lines, refactor it to minimal structure" assistant: "I'll use the agent-creator skill to refactor this into a minimal ~150 line agent with a separate skill file" <commentary>Agent refactoring requires the agent-creator skill to separate identity from technical procedures.</commentary></example>

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

RED-GREEN-MUTATE-KILL MUTANTS-REFACTOR workflow for writing production code. Use before ANY production code change - new features, bug fixes, or behavior changes. Triggers on starting implementation work of any kind. Covers the cycle itself - failing test first, minimum code to pass, mutation verification, refactor assessment. For how to write good tests, see testing. For the refactoring step in detail, see refactoring. TDD is non-negotiable.

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

Intelligent refactor command. Triggers: refactor, refactoring, cleanup, restructure, extract, simplify, modernize.

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

Autonomous comprehensive refactoring. Three-phase pipeline — Phase 1 /refactor (tactical, loops internally to convergence) → Phase 2 loop of /review-arch + /implement-batch until architectural findings converge below a severity floor (default HIGH+) → Phase 3 /refactor (catches tactical issues introduced by restructuring). Auto-approves /review-arch ticket proposals; pulls the andon cord on contested findings, breaking-change proposals, repeated implementation failure, or Phase-2 hard-cap exhaustion (5 architectural iterations).

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

Use when the user asks for a phase-gated refactoring or redesign loop - session-blind workers map and trace the area, empirical probes precede the design, an approval gate guards implementation, and a conformance audit re-checks the branch after any design change. State persists in .episteme/DESIGN-<slug>.md. Requires the refactor agent roles registered by scripts/install-codex.sh. Keywords: refactor loop, redesign, design gate, enumerate before design, conformance audit.

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

대화형 System-wide Refactoring — 변경 파일에서 Extract Method·Domain Logic 이동·Pull Up 등 클래스 경계를 넘는 구조 변경 후보를 찾아 승인 후 기법별 커밋으로 적용. "구조 리팩토링", "도메인 로직 이동", "클래스 분리", "system-wide", "/system-wide-refactoring" 요청 시 사용. 단, 메서드 내부 정돈(guard clause·extract variable 등)은 /tdd-tidy가 적합. /system-wide-refactoring [commit-ref]로 호출.

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

統合リファクタリングエージェント - 既存システムをマイクロサービスアーキテクチャにリファクタリングするための統合分析・設計を実行。/refactor-system [対象パス] で呼び出し。

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

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

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

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...

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

Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.

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

[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.

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

Create a Beads-first refactor plan through detailed interview, repo verification, alternatives, scope boundaries, testing decisions, and tiny working increments. Use when the user wants to plan a refactor, write a refactoring RFC, or turn a risky change into safe incremental work.

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

Develop and refactor Quarkus 3.x LTS services by writing tests first. Covers API responses, event handling, and asynchronous operations, with unit and integration tests plus coverage checks to show how much code is tested.

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

• Adding REST endpoints with tests first
• Reproducing bugs before fixing them
• Testing Apache Camel routes and event handling

업무 로직을 데이터베이스, 외부 API, 프레임워크에서 분리합니다. 경계와 테스트를 정리해 새 서비스를 설계하고 기존 코드를 기능별로 단계적으로 개선하도록 지원합니다.

• 업무 규칙과 데이터베이스·API 호출 분리
• HTTP·CLI·워커에서 처리 공유
• 업무 규칙을 유지하며 외부 기반 교체

Write, review, and refactor modern C++ using the C++ Core Guidelines. Covers type safety, automatic resource cleanup, class design, exceptions, concurrency, and naming conventions, with examples and a checklist for identifying unsafe or inconsistent code.

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

• Writing modern C++ classes and functions
• Reviewing memory ownership and resource cleanup
• Refactoring existing C++ code

Guide coding, reviews, and refactoring with explicit assumptions, simple implementations, focused changes, and testable goals. These behavioral guidelines help an AI agent avoid unnecessary complexity and verify that its changes meet the request.

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

• Clarifying assumptions before implementation
• Keeping bug fixes focused
• Reviewing code for unnecessary complexity