'refactor' 검색 결과

[omh] Decided cross-module refactor to phase: refactor planning - turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.

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

[omh] Oversized or tangled UI component: behavior-preserving refactor of UI code - preview the full change plan first, apply as a second explicit step, and work impact-ordered from state architecture down to naming polish. Use when the user says: frontend-refactor, front-refactor, frontend refactor, refactor this component, refactor the component, refactor my component, component refactor, react refactor.

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

Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.

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

• Finding refactoring candidates and unreferenced code
• Previewing edits before applying a rename
• Checking affected dependencies and execution paths

Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named refactorings, and the full suite re-run after every step. Use when the user wants to refactor, restructure, clean up, simplify, or improve the design of existing code, or to apply refactoring recommendations from a code-review or architectural-analysis report. This skill changes code; it does not review code (use code-review), assess architecture (use architectural-analysis), plan a multi-module restructure before executing it (use plan-a-change), map domain boundaries before restructuring along them (use ddd-analysis), or build new behavior test-first (use tdd). Do not use it on code inside an active tdd loop; the refactor step of tdd owns that cleanup. Runs its planned sequence to completion without pausing for review; to review each named refactoring as it lands, use pairing.

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

Run multiple Reforge-guided section-refactor lanes in parallel, each in its own worktree/branch off origin/main, with a score-blind adversarial review panel gating every commit, one draft PR per section. Use when the user wants to reduce Reforge surface/internal score across several sections at once via architecturally-correct deletions (dead surface, entity-leak removal, cross-section consumers moved onto the public contract) — not by relocation, parameter bags, or accessibility-dodging. Wraps the per-lane process in .codex/skills/humans-refactor. Triggers: 'refactor swarm', 'parallel section refactors', 'run reforge refactor on Users/Tickets/...', 'burn down surface score across sections'. Has an intensity dial (light|standard|deep) and a workflow|solo execution mode to trade token burn against autonomy per unit of output.

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

Coordinate code refactoring, restructuring code while preserving its behavior. Check existing tests before changes, work in small steps, review the result, and pause for approval of the plan and before committing.

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

• Extracting a module without changing behavior
• Removing duplicate or unused code
• Reducing nesting and clarifying names

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

Safely refactors C#/.NET code without changing behavior. USE FOR any request to refactor, rename, move, extract, inline, merge, consolidate, deduplicate, split, or modernize C# code, including partial/generated declarations, wrappers, public APIs, serialization/reflection/configuration names, friend assemblies, conditional compilation, and multi-targeted projects. Also use when a request calls a feature, bug fix, package/framework upgrade, or public nullability change a refactor and the behavior-changing part must be separated or declined. DO NOT USE FOR ordinary feature or bug fixes not presented as refactoring; standalone upgrades after reclassification (use dotnet-upgrade); adding tests; or formatting-only work.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Safely refactors C#/.NET code without changing behavior. USE FOR any request to refactor, rename, move, extract, inline, merge, consolidate, deduplicate, split, or modernize C# code, including partial/generated declarations, wrappers, public APIs, serialization/reflection/configuration names, friend assemblies, conditional compilation, and multi-targeted projects. Also use when a request calls a feature, bug fix, package/framework upgrade, or public nullability change a refactor and the behavior-changing part must be separated or declined. DO NOT USE FOR ordinary feature or bug fixes not presented as refactoring; standalone upgrades after reclassification (use dotnet-upgrade); adding tests; or formatting-only work.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.

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

Cursorでローカルの差分・ファイルからリファクタリング改善案を返すnative入口。変更は適用せず、共有refactor-advisorとrefactor-guidanceを読み、reviewerのVERDICTから分離する。

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

Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

SKILL.mdを最も効率的に動作するよう整理するスキル。 7ステップのリファクタリング手順でスキルの実行効率・コンテキスト効率を最適化する。 Trigger: スキル整理, SKILL.md圧縮, スキルリファクタ, skill refactor, refactor skill

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

Develop features and fix bugs by running a failing test first, making the smallest passing change, then refactoring. Check at least 80% test coverage and preserve evidence of failures, successful fixes, and verified behavior.

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

• Implementing a new feature from tests
• Reproducing a bug before fixing it
• Refactoring code while keeping tests passing

Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.

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

• Adding features with tests written first
• Reproducing a bug in a test before fixing it
• Refactoring while keeping tests passing

Guide Rust development through test-driven development: write a failing test, implement enough code to pass, then refactor. Includes practical test patterns and final checks for formatting, static analysis, and test results.

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

• Adding Rust features with tests first
• Reproducing bugs with failing tests before fixing them
• Testing invalid inputs and error paths

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

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