Results for “simplify”

Review changed Anabasis v2 code for reuse, simplification and efficiency, then apply the fixes. Report correctness bugs separately. Starts from the lint plugins, the whole-tree census and the not-slop ledger, measures before and after with reduce-complexity's scripts, and holds a pass to its budgets and the repository's rules. 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.

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

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.

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

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, コード整理, リファクタ, 複雑さ削減, コードレビュー.

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

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.

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

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.

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

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.

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

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.

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

await 漏れ・floating promise・並行競合など、非同期処理の correctness バグを検出する。並列化の効率提案（SIMPLIFY Efficiency）や配線断点（e2e-wiring）ではなく、「await を忘れて結果・順序・エラー伝播が壊れる」実装バグに限定する

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

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".

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

ローカル変更（未コミット/ステージ済み）を Claude + Codex + security + simplify の 4 観点で並列レビューし統合結果を表示。「ローカルレビュー」「変更をレビュー」「コミット前レビュー」「手元の変更をチェック」「review」などで起動。GitHub の PR ではなく作業中の変更が対象。

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

Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.

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

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.

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

Parallel 3-agent cleanup of recent code changes.

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

Review new and existing software tests for the behavior and regressions they actually protect. Identify duplicate or implementation-dependent checks, document evidence before removal, and simplify code used only by tests while retaining meaningful coverage.

• Checking whether a new test adds useful coverage
• Auditing duplicate or implementation-dependent tests
• Reviewing code exposed only for testing

Review a coding session and identify improvements to the agent’s working environment. Examine file navigation, automated checks, instructions, tool use, and information access, then present proposed changes in order of severity.

• Reviewing a coding session that took too long
• Finding automated checks for recurring mistakes
• Simplifying agent instructions

Rewrite technical documentation and instructions using ASD-STE100, a set of rules for clear technical English. Shorten sentences, keep terminology consistent, and audit passages with rule numbers and suggested corrections while preserving code and commands.

• Simplifying English README files and operating procedures
• Auditing technical text against STE rules
• Clarifying error messages and incident reports

Review recent code changes from four angles: reuse, quality, efficiency, and whether fixes address underlying mechanisms. Combine findings, apply suitable cleanup with tests, and leave changes that could affect behavior for human review.

• Cleaning up recent code changes
• Finding duplicated logic and reusable helpers
• Reviewing efficiency in the last commit

Review code changes before merging across correctness, readability, architecture, security, and performance. Get findings that distinguish required fixes from optional suggestions, with concrete ways to simplify code and checks on test coverage.

• Reviewing a pull request before merging
• Checking code written by an AI agent
• Assessing whether a refactor reduces complexity

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

Design and improve website and app interfaces, from typography, spacing, and color to task flows. Review usability, accessibility, responsive layouts, and performance, or refine interface text, error states, and reusable design elements.

• Planning the structure and appearance of a new interface
• Improving typography, spacing, and color in existing screens
• Reviewing accessibility and layouts across screen sizes

Keep coding changes small by questioning unnecessary work and reusing existing code, standard libraries, and native platform features. Apply this approach to implementation, bug fixes, reviews, and dependency choices while preserving validation, security, and accessibility.

• Reduce unnecessary code and dependencies
• Fix shared root causes of bugs
• Review code for excessive abstraction

Audit website redirects after URL migrations, domain changes, or CMS upgrades. Record each redirect path and HTTP status code, identify unnecessary steps or loops, and update redirects to point directly to the final destination.

• Checking redirect paths after a URL migration
• Finding redirect chains and loops after a domain change
• Simplifying redirect rules accumulated through CMS upgrades

Measure the size and nesting of a page's DOM, the tree of HTML elements. Identify unnecessary wrappers and oversized lists, then simplify the structure or render only visible list items to reduce confirmed rendering costs.

• Investigating pages with slow rendering or interactions
• Measuring HTML element counts and nesting depth
• Removing unnecessary wrapper elements

Clean up AI-generated code in branch changes or selected files while preserving behavior. Establish passing regression tests first, then remove unnecessary code and complexity, run project quality checks, and report both changes and skipped issues.

• Cleaning up recent AI-generated changes
• Removing redundant comments and dead code
• Simplifying duplication and excessive complexity