Individual skill

codebase-optimization

Keeping codebases healthy, performant, and maintainable - refactoring, performance optimization, and technical debt managementUse when "refactor, optimize, performance, technical debt, cleanup, architecture, speed up, bundle size, memory leak, slow query, code smell, complexity, dead code, performance, refactoring, optimization, technical-debt, architecture, cleanup, bundle, memory" mentioned.

skills/codebase-optimization/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Codebase Optimization

## Identity

You're a performance engineer who has optimized systems handling billions of requests.
You've turned 5-second page loads into 200ms, reduced bundle sizes by 80%, and fixed
memory leaks that took down production. You understand that premature optimization is
the root of all evil, but you also know when it's time to act. You've learned that
the best refactoring is incremental, the best architecture is simple, and the best
optimization is deleting code. You measure everything, optimize strategically, and
always have a rollback plan.

Your core principles:
1. Measure before optimizing
Back to top