Results for “simplify”

This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.

The English summary is being prepared. Showing the original description.

Review recent code changes for duplication, maintainability, and wasted work, then apply straightforward improvements. The workflow combines three parallel reviews, prioritizes small, low-risk fixes, and checks the edited code with relevant tests or project checks.

• Cleaning up code after implementation
• Polishing changes before opening a pull request
• Reducing duplication in recent changes

Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes. Use when the user asks to "simplify all", "simplify everything", "simplify code and docs", "clean up code and docs", "run both simplify skills", or "simplify code and docs in parallel".

The English summary is being prepared. Showing the original description.

Run the code and documentation simplification passes together over one scope, launching every review sub-agent concurrently before applying a single round of fixes. Use when the user asks to "simplify all", "simplify everything", "simplify code and docs", "clean up code and docs", "run both simplify skills", or "simplify code and docs in parallel".

The English summary is being prepared. Showing the original description.

Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.

The English summary is being prepared. Showing the original description.

Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

The English summary is being prepared. Showing the original description.

Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

The English summary is being prepared. Showing the original description.

Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers comments that misdescribe the code, what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "fix stale comments", "reduce doc noise", or "run simplify-docs".

The English summary is being prepared. Showing the original description.

Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

The English summary is being prepared. Showing the original description.

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 and simplify code while preserving its behavior. Check readability, reuse, and efficiency, assess whether tests and comments add value, and verify applied changes with the project's configured checks before review.

• Cleaning up code after implementation
• Improving readability before code review
• Auditing tests for practical value

Simplify cluttered interfaces by reviewing information, visual styling, interactions, copy, and code. Keep essential functionality and accessibility while clarifying the main action, consolidating related elements, and revealing secondary details only when needed.

• Decluttering a screen with too many competing buttons
• Reducing unnecessary colors, borders, and nested cards
• Shortening forms and simplifying interaction steps

AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability. Use when users ask to simplify code, reduce complexity, refactor for readability, clean up implementations, improve maintainability, reduce technical debt, or make code easier to understand.

The English summary is being prepared. Showing the original description.

Simplify code, plans and systems without losing required outcomes; delete machinery that earns nothing; for code, AST-measured complexity with regression gates. Triggers: simplify, refactor, complexity, overengineered, dead code, useless guard.

The English summary is being prepared. Showing the original description.

SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on "simplify skill", "optimize skill", "skill-simplify".

The English summary is being prepared. Showing the original description.

Review changed code for reuse, quality, and efficiency, then fix any issues found. Sizes review effort to the diff — trivial edits get a self-review, substantial edits get parallel agents. Renamed from /simplify to avoid collision with Claude Code's built-in simplify skill.

The English summary is being prepared. Showing the original description.

Post-implementation simplification pass. Reduces complexity without changing behavior. Use after Phase 3 (Build GREEN) and before Phase 4 (Review). Catches dead code, unnecessary abstractions, over-engineering, and redundant patterns. Triggers on "simplify", "clean up", "reduce complexity", "too complex". NOT for style/convention enforcement (see mk:clean-code); NOT for reviewing diffs or PRs (see mk:review).

The English summary is being prepared. Showing the original description.

Unified pull request workflow: prepare a safe branch, run read-only review, fix Required findings, create/update a GitHub draft PR, and verify CI plus automated review comments. Subcommands: `create` (simplify + PR, skip code review), `review` (read-only findings only), `fix` (Required fixes + commit, no push), `simplify` (simplification only), `verify` (existing PR checks/reviews only). Use when creating or reviewing PRs, self-reviewing changes, simplifying PR changes, or requesting "PR作成", "レビュー", "簡素化". Do NOT use for responding to review comments or a lightweight review of the current working diff without the PR workflow (use the built-in /code-review instead).

The English summary is being prepared. Showing the original description.

Reduce changes on your own branch before opening or updating a pull request. Review added architecture and tests, remove unnecessary complexity, and verify that the smaller change still fixes the original problem and preserves supported behavior.

• Trim changes before opening a pull request
• Remove duplicate architecture after a large repair
• Keep tests that catch distinct failures

Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.

• Simplifying a module's interface
• Bringing scattered complexity into one module
• Choosing where implementations can be swapped

Review website text and interface instructions for jargon, complex sentences, and unclear actions. Simplify wording, explain technical terms, and adjust reading difficulty so the intended audience can understand content and follow instructions.

• Simplifying website instructions
• Explaining technical terms for general readers
• Reviewing interface text for accessibility

Review blog posts, landing pages, and guides for readability. Estimate reading difficulty, identify long sentences and jargon, and simplify wording and paragraph structure so broad audiences can follow the content more easily.

• Checking a blog post for readability
• Simplifying landing page copy
• Rewriting jargon in a how-to guide

Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.

• Extracting validation logic into a separate module
• Renaming symbols across related files
• Simplifying conditionals and repeated patterns

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