263 skills · sorted by relevance
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.
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.
Guides Avalonia interface layout with Zafiro.Avalonia, using shared styles, reusable components, and purpose-specific containers. Helps reduce repeated XAML, the markup used to define interfaces, and simplify deeply nested layouts.
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.
Calculate change risk for a specific .NET method, class, or file by combining code complexity with measured test coverage. Get ranked results and recommendations on where to add tests or simplify logic.
Provides coding conventions for TypeScript, JavaScript, React, and Node.js. It guides naming, type safety, error handling, API structure, and tests, with examples for simplifying complex functions and keeping code consistent and maintainable.
Review system architecture using implementation, callers, and tests as evidence. Compare interface designs, clarify how components should interact, and receive a recommendation with migration steps and test implications before deciding whether to refactor.
Refactor code through a staged process that maps dependencies, assesses test coverage, and plans small changes. Use it to extract functions, simplify code, or restructure modules while checking tests and diagnostics throughout.
Review existing charts for clear communication, appropriate chart types, readable labels, scales, and color choices. Get concrete suggestions for simplifying layouts, improving accessibility, and making the visualization suit its intended audience.
Perform arithmetic, algebra, calculus, matrix operations, number theory, and statistics with SymPy, a symbolic mathematics library. Return exact expressions, numerical values, and LaTeX notation for checking calculations or using results in other work.
Organize multi-agent reviews with defined roles for bugs, architecture, integration, and usability. Designed for local Codex workflows with vibe, it combines findings by severity into a shared set of keep, simplify, or remove decisions.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Simplify existing code for clarity and maintainability without changing behavior. Use when asked to clean up or simplify code, especially recent changes.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Simplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.
The English summary is being prepared. Showing the original description.