'simplification' 검색 결과

Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.

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

• Finding code that can be safely removed
• Consolidating duplicated state or APIs
• Reviewing obsolete compatibility paths and design records

Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.

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

• Finding unused code and unnecessary internal APIs
• Reviewing duplicated stores, caches, and events
• Assessing library replacements that reduce maintenance

Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.

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

Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.

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

Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle ownership. Use when asked to simplify or clean up a repository, reclaim code entropy, reduce over-engineering or redundancy, find deletion candidates, collapse duplicate state/APIs, remove dead or added-then-abandoned code beyond static-tool output, or implement an evidence-backed simplification pass in any language or stack. Also trigger for 代码化简、熵回收、删代码、清理冗余、收敛抽象、去除过度设计. Do not use as a performance audit unless simplification is the stated goal.

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z

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

Simplify application code for clarity without changing behavior — refactor after tests pass, reduce nesting and duplication, match project conventions. Load when refactoring for readability, cleaning up after a feature ships, or when code review flags complexity. Also triggers on "simplify this code", "code simplification", "make this easier to read", "reduce complexity", "refactor for clarity". Not for compress/split/prune-skill (skill-library files). Pairs with technical-debt-audit.

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

Make working code easier to read and maintain while preserving its behavior. The skill identifies tangled conditions, unclear names, duplication, and unnecessary abstractions, then guides small refactoring steps checked against existing tests and project conventions.

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

• Improving readability after a feature is working
• Addressing complexity raised in code review
• Untangling nested conditions and long functions

Simplify Rust code in RTK by replacing verbose loops, unnecessary copies, and excessive abstractions with common Rust patterns. Preserve behavior and project requirements, including error context, fallback handling, exit codes, and existing test modules.

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

• Simplifying verbose loops and string construction
• Removing unnecessary string copies
• Reducing nested conditional and error handling code

Review changed code from four angles: reuse, simplicity, efficiency, and whether fixes address the underlying mechanism. Applies suitable improvements within the reviewed scope while preserving intended behavior, and reports fixes or skipped findings.

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

• Clean up code changes before committing
• Replace duplicated logic with existing helpers
• Reduce redundant computation and repeated I/O

Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.

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

• Review uncommitted changes for bugs
• Check a pull request or branch before merging
• Find duplicated logic and unnecessary work

Review the journey from discovering an API to receiving the first successful response. Identify delays in signup, authentication, setup, and documentation, then plan improvements using test environments, interactive examples, clearer errors, and measurements of progress.

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

• Auditing the path to a first successful API call
• Simplifying signup and access to test API keys
• Planning sandbox environments and interactive documentation

Review completed code changes for defects, security risks, unnecessary complexity, and missing tests. Findings are verified and reported with severity, file locations, and concrete failure scenarios, with separate assessments of standards and intended behavior for larger changes.

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

• Checking completed changes before release
• Reviewing compliance with documented development standards
• Checking implementation against ticket requirements

Find unused components, files, translation keys, and other unnecessary code across a codebase. Document every consumer and removal impact in a tracking issue, then turn one maintainer-approved candidate into a focused pull request.

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

• Periodically checking for accumulated unused code
• Finding orphaned translation keys
• Recording removal candidates and their impact in an issue

Review a pull request, a proposed code change, for code that can be removed or simplified. Consider product decisions, final functionality, and whether rare edge cases have led to unnecessary complexity.

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

• Review a pull request for simplicity
• Find code that could be deleted
• Reconsider overcomplicated handling of rare cases

Review code changes for unnecessary complexity, including unused flexibility, avoidable dependencies, and abstractions with little purpose. Receive concise findings that name what to remove, what can replace it, and how many lines could be cut.

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

• Check code changes for over-engineering
• Find code replaceable with standard library features
• Identify unnecessary dependencies and abstractions

Audit an entire codebase for unnecessary complexity and dependencies. Receive a ranked list of code to delete, simplify, or replace with standard library and platform features, with file paths and estimated reductions.

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

• Finding code and dependencies to remove
• Reviewing abstractions that add little value
• Identifying replacements using built-in features

Review and simplify the ego-lite codebase by finding unused code, duplicated state, and unnecessary layers. The skill checks real callers and API requirements, explains behavior changes, and coordinates implementation, tests, and documentation updates.

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

• Audit unused code and APIs
• Consolidate duplicated state or processing
• Review unnecessary compatibility layers

Review the exact final set of changes for a LoopX goal, checking reuse, simplification, concrete risks, and project validations. Record and verify a quality receipt, a review record tied to those specific changes.

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

• Reviewing final changes before delivery or merge
• Checking reuse and opportunities to simplify code
• Recording validation results and concrete quality risks

Work through repeated failed fixes or difficult technical choices using five perspectives: practical action, missing information, simplification, architecture, and challenged assumptions. Compare alternatives and disagreements, then receive a recommendation while keeping the final decision with the user.

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

• Reconsider a fix that has failed repeatedly
• Compare difficult database or architecture choices
• Reduce scope when complexity blocks progress

在 codexhost 中寻找有证据支撑的简化候选：无生产调用方的接口、镜像表示、为未来而设计的通用性、可由依赖或内置能力替代的手写代码。默认只读，输出带证据的候选清单；用于审计 AI 辅助开发造成的过度设计，不用于实现新功能。

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

Review a skillshare change before it becomes a pull request, or review an open pull request. Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed. It checks correctness, the repository's documented rules, the originating issue or spec, every consumer of a changed concept, and cleanup (reuse, simplification, efficiency, depth of fix), then verifies each finding against the code before reporting it. Read-only unless the user asks for fixes.

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

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

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

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