'refactoring' 검색 결과

Guide AI coding work toward simple implementations, focused edits, and explicit assumptions. Use it when writing, reviewing, or refactoring code to keep changes tied to the request and define success through tests or other concrete checks.

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

• Keeping bug fixes limited to the necessary code
• Simplifying code that has become overcomplicated
• Making implementation assumptions explicit

Improve existing code without changing its behavior. This skill guides analysis, test checks, identification of design problems, and a phased refactoring plan, then applies small changes with testing and review.

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

• Breaking long functions into smaller parts
• Consolidating duplicated logic
• Planning cleanup of legacy code

Improve existing code structure while preserving its behavior, using Martin Fowler's refactoring approach. Assess tests, identify structural problems, agree on a phased plan, and make small, tested changes with reversible commits and before-and-after comparisons.

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

• Splitting long functions into clearer responsibilities
• Removing duplicate or unused code
• Planning gradual improvements to legacy code

Review code for security, performance, quality, and maintainability. Get findings organized by severity, with file locations, explanations of impact, and example fixes, plus code metrics and complexity comparisons for refactoring reviews.

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

• Reviewing a pull request before merging
• Checking code for security risks
• Finding performance improvement opportunities

Improve existing code without changing its behavior. This skill guides analysis, test checks, identification of design problems, and a phased refactoring plan, then applies small changes with testing and review.

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

• Breaking long functions into smaller parts
• Consolidating duplicated logic
• Planning cleanup of legacy code

Plan Codewhale changes by locating the existing implementation and its callers, defining one reviewable change, and choosing verification before editing. Use it for features, upgrades, and refactoring to avoid duplicate implementations and unfinished migrations.

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

• Locate existing code before adding a feature
• Define a reviewable scope for refactoring
• Choose checks before implementation

Refactor JavaScript using ES6+ features to make code easier to read and maintain. Covers asynchronous operations with async/await, modules, and functional patterns that transform data without changing the original values.

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

• Refactoring legacy JavaScript
• Migrating callbacks to async/await
• Building data transformation pipelines

Refactor Java methods by extracting related blocks into separate, clearly named methods. Assess method length and complexity, preserve existing functionality, and return complete Java 17 methods with brief comments explaining each newly extracted method.

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

• Split a long Java method into smaller methods
• Separate distinct operations within complex methods
• Name extracted logic to clarify its purpose

Simplify Java methods and constructors by removing unused or redundant parameters. The skill adjusts definitions and internal calls, preserves existing functionality, and returns complete Java 17 code with comments explaining each removed parameter.

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

• Remove unused parameters from Java methods
• Simplify constructor parameter lists
• Review parameters whose values are available elsewhere

Compare two versions of a project and turn migration patterns into instructions for GitHub Copilot. Document API replacements, new conventions, obsolete patterns, and validation steps so future code changes follow the same approach.

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

• Documenting framework version upgrades
• Creating rules for replacing a technology
• Preserving conventions after architectural refactoring

Organize Node.js, Express, and TypeScript APIs into layers with clear responsibilities. This guide covers request handling, business logic, database access, input validation, error tracking, configuration, and testing to support consistent implementation and refactoring across services.

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

• Adding an API endpoint with clearly separated responsibilities
• Organizing database access through Prisma
• Adding input validation and error tracking

Write, review, or refactor React code using prioritized guidance for data fetching, bundle size, rendering, component structure, testing, and type safety. Start with high-impact issues such as sequential requests and unnecessary library loading.

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

• Writing React components and data-fetching logic
• Reviewing code for loading and rendering performance
• Refactoring large components and overly broad interfaces

Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.

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

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Refactor Handsontable code by separating plugin responsibilities, reducing dependencies, batching rendering work, and updating coding patterns. It provides compatibility rules and testing guidance to preserve existing APIs, CSS classes, settings, and behavior.

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

• Split an oversized plugin into focused plugins
• Reduce repeated rendering during bulk updates
• Update private fields and callback patterns

Keep coding tasks small by checking whether new code is needed, reusing existing helpers, and preferring standard libraries or built-in platform features. Apply the same approach to feature development, bug fixes, refactoring, and reviews.

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

• Adding a feature with minimal code
• Reviewing unnecessary dependencies
• Simplifying an overcomplicated implementation

Implement Verdaccio fixes, features, or refactoring after checking whether existing settings or plugins already solve the problem. Place changes in the responsible component, reuse helpers, add tests and release notes, and validate affected packages.

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

• Implementing a bug fix with a regression test
• Checking existing settings before adding a feature
• Refactoring code within a defined change

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

Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.

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

• Adding an API endpoint
• Separating business logic from database access
• Standardizing input validation and error handling

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

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

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

Find business logic repeated across software components, such as notifications, auditing, and validation. Compare responsibilities and dependencies, then recommend a shared service, shared library, or component merger with a prioritized consolidation plan.

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

• Finding duplicate business logic before refactoring
• Reviewing whether notification components should be merged
• Identifying candidates for shared services or libraries

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