agentsclimarketplace

Complexity optimizer

Skill markoblogo/abvx-agent-skills/skills/complexity-optimizer

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill complexity-optimizer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze or improve codebase complexity and performance hotspots without broad rewrites. Use when reviewing nested loops, repeated scans, N+1 queries, rendering churn, excessive recomputation, slow tests, large-input paths, memory pressure, or requests to reduce complexity while preserving behavior and tests.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

Complexity Optimizer

Optimize only when behavior is understood and can be preserved. A small measured improvement beats a clever rewrite.

Modes

  • Report mode: rank opportunities and do not edit.
  • Implementation mode: change scoped code after identifying a repro, test, benchmark, or reviewable invariant.
  • Audit mode: scan broad areas, then inspect only the highest-impact leads.

Workflow

  1. Establish scope: language, framework, hot paths, data sizes, tests, build command, and user-facing risk.
  2. Find leads: nested scans, repeated filtering, loops inside render paths, N+1 database/API calls, redundant serialization, unbounded recursion, cache misses, and avoidable work in hooks or lifecycle methods.
  3. Rank by likely impact and blast radius. Treat static findings as leads, not proof.
  4. For each serious finding, record:
    • file and location;
    • current pattern;
    • estimated current complexity;
    • proposed change;
    • expected complexity after change;
    • correctness risk;
    • verification needed.
  5. Before editing, preserve behavior with existing tests, a focused regression test, a fixture, or a clear invariant.
  6. Optimize conservatively:
    • replace repeated linear lookup with maps or sets when equality is stable;
    • pre-index or group data before joins;
    • batch database/API access while preserving tenant, permission, filtering, ordering, and pagination;
    • memoize derived UI data only when inputs are stable;
    • virtualize or paginate large rendered collections;
    • avoid caches without invalidation strategy.
  7. Run narrow checks first, then broader relevant checks.

Safety Checklist

Before finalizing:

  • output ordering is preserved or intentionally changed;
  • duplicates and null/missing values are handled;
  • mutation and object identity assumptions are not broken;
  • authorization and tenant filters survive batching;
  • cache invalidation is explicit;
  • the original performance or failure signal was rerun.

Final Report

Include:

  • top findings or changed files;
  • before/after complexity estimates;
  • verification commands and results;
  • residual risks and missing measurement gaps.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.