'refactor' 검색 결과

Write and refactor C++20/23 applications, addressing memory management, concurrency, and performance bottlenecks. Produce interfaces, implementations, tests, and relevant CMake updates, then check runtime errors and measure performance before applying targeted optimizations.

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

• Refactoring existing code with C++20/23 features
• Investigating memory errors and undefined behavior
• Improving performance through profiling and benchmarks

Review code changes and files for bugs, security risks, performance problems, design issues, and test coverage. Receive a structured report with prioritized findings, concrete improvement examples, positive feedback, and an overall review verdict.

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

• Reviewing a pull request
• Auditing code quality and security
• Finding refactoring opportunities

Identify maintenance problems across code, architecture, tests, dependencies, documentation, and infrastructure. Rank them by impact, risk, and effort, then produce a prioritized backlog with business reasons and a phased improvement plan alongside feature development.

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

• Deciding which parts of the codebase to refactor first
• Organizing maintenance issues across technical areas
• Explaining the business reasons for technical improvements

Write, review, and refactor Python code using concrete readability rules. Keep functions focused, reduce nested logic, clarify names and expressions, and apply Python features such as comprehensions, dataclasses, and pathlib while respecting existing codebase conventions.

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

• Refactoring long functions and deeply nested logic
• Reviewing names and complex expressions
• Organizing code with Python standard library features

Build, refactor, and troubleshoot ChatGPT apps with an MCP server, which exposes tools to the assistant, and an interactive widget. Use official documentation and examples to plan tools, scaffold code, configure security settings, and validate local operation.

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

• Scaffolding a ChatGPT app with a server and widget
• Planning app tools and their inputs
• Refactoring an existing Apps SDK demo

Refactor large SwiftUI screens into smaller views with clear inputs and state ownership. Organize actions, shared dependencies, and observable models while preserving existing layout and behavior, making the code easier to read and test.

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

• Split a large SwiftUI screen into smaller views
• Clarify state ownership and data flow
• Move business logic out of the view body

Build or refactor SwiftUI screens using component examples for navigation, state, layouts, and controls. The skill guides screen composition, asynchronous loading, previews, and build checks while following existing project conventions and supported operating system versions.

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

• Set up tabs, navigation, and sheets in a new app
• Refactor large screens into focused subviews
• Clarify state ownership and dependency sharing

Refactor large macOS SwiftUI views into focused files and components. Clarify window state, selection, commands, and AppKit integration while preserving existing behavior and keeping the main layout stable as users change selections.

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

• Split oversized SwiftUI views
• Organize state for each window
• Extract toolbar and command logic

Apply Vercel Engineering’s performance guidelines when writing, reviewing, or refactoring React and Next.js code. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering using rules with explanations and code examples.

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

• Review React components for performance issues
• Improve data fetching in Next.js pages
• Reduce downloaded code and loading time

Write, review, and refactor React and Next.js code using performance guidelines from Vercel Engineering. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering, with rule files providing explanations and code examples.

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

• Reviewing React code for performance issues
• Reducing delays in Next.js data fetching
• Reducing downloaded code size and load times

Review domain code for classes that hold data while business logic lives elsewhere. Using domain-driven design patterns, diagnose problems and refactor objects to keep business rules, state changes, and validation together, with before-and-after diffs.

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

• Reviewing domain models against DDD patterns
• Finding classes that only hold data
• Moving business rules into domain objects

Guide an AI agent through code changes with explicit assumptions, simple implementations, focused edits, and testable goals. Use it for bug fixes, features, refactoring, or reviews to reduce guesswork and unnecessary changes.

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

• Fixing a bug with a test that reproduces it
• Adding a feature without expanding its scope
• Refactoring while preserving existing behavior

Investigate unfamiliar codebases before fixing bugs, adding features, or refactoring. Follow relevant code paths, plan focused changes, and verify results, while recording useful discoveries in .notebook/ so later sessions can build on earlier investigation.

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

• Investigate and fix bugs in unfamiliar code
• Add features following existing project conventions
• Trace and document authentication or other flows

Refactor React components that have too many true-or-false settings into reusable, flexible parts. This skill guides component composition, shared state, and API design, with examples and separate guidance for React 19 features.

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

• Refactoring components with many boolean props
• Designing a reusable component library
• Organizing state shared by sibling components

Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.

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

Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.

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

[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.

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

Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.

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

Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

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

Refactor code while preserving passing tests and behavior. Use during the TDD refactor phase to remove duplication, improve design, and verify each structural change.

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

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.

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

Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).

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

Refactor code to improve structure and maintainability

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

Pre-refactor safety checklist. Verifies test coverage exists before AI modifies existing code. Use before asking AI to refactor anything.

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