237건 · 관련도순
Simplify code once its behavior is understood. Confirm the existing behavior through tests or reproduction, reduce unnecessary complexity in small, reviewable steps, and keep verification passing while preserving behavior and necessary safety checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use WorldMonitor’s architecture as a reference for building dashboards. Find examples of TypeScript panels, data services, grid layouts, API proxies, and refresh scheduling, with guidance on simplifying these patterns for a personal monitoring project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Keep code, tests, documentation, configuration, and other changes as tight, clear, performant, and minimal as possible without weakening behavior. Use during implementation to prevent unnecessary complexity, after behavior is proven to consolidate working changes, before handoff for a full branch audit, and when asked to simplify, tighten, clean up, reduce verbosity, remove complexity, or minimize existing work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use when a feature has just landed ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup pass before review. Produces a smaller, flatter version with identical behaviour, plus a ledger of what was removed and why it was safe. For finding bugs use code-review-checklist / ai-code-review — this skill assumes it works and makes it simple.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically simplify and minimize TLA+ specifications by reducing redundant state variables, merging equivalent actions, and minimizing invariants while preserving specified properties. Use when working with TLA+ specifications that need optimization, simplification, or reduction. Triggers when users ask to minimize, reduce, simplify, or optimize TLA+ specs, or when they want to remove redundancy from formal specifications while maintaining semantic equivalence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplify existing code for clarity and maintainability without changing behavior. Use when asked to clean up or simplify code, especially recent changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review changed Anabasis v2 code for reuse, simplification, efficiency and altitude, then apply the fixes. Quality only: it hunts no bugs, which /code-review does. Starts from what the repository already finds (the lint plugins, the whole-tree census, the not-slop ledger), measures before and after with reduce-complexity's scripts, and holds a pass to its budgets and to the rules no pass trades. Use as /simplify on your own diff before a commit, or when the operator asks whether code is simple enough, why something exists, to go one layer higher, or to remove something and find another way.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says "simplify this diff" or asks for a compression pass over a change-set. Not for dead-code sweeps: use deslop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for simplifying and refining code after coding sessions. Use when cleaning up complex code, reviewing PRs for readability, or applying consistent refactoring patterns. Triggers on simplify code, refactor, clean up, code review, コード整理, リファクタ, 複雑さ削減, コードレビュー.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run code quality checks (ruff, mypy, pytest) and optionally simplify code. This skill should be used when the user wants to check code quality, run linters, run tests, or simplify recently modified code. Triggered by /lint, /check, or /code-quality commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs synapse-docs, /simplify, sync-plugin-skills, and github-pages-sync in parallel for synapse-a2a development workflows. Use when you need doc updates, code simplification, plugin skill sync, and site-docs sync at the same time.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow Phase 7 — Mechanical cleanup pass over the branch diff, followed by a `code-structure` review pass and a `verify` re-stamp. Shadows the global `simplify` skill at project scope; the cleanup pass is performed inline rather than via Skill self-call.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
await 漏れ・floating promise・並行競合など、非同期処理の correctness バグを検出する。並列化の効率提案（SIMPLIFY Efficiency）や配線断点（e2e-wiring）ではなく、「await を忘れて結果・順序・エラー伝播が壊れる」実装バグに限定する
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.