performance-optimizer
/performance-optimizer
Analyze codebase for performance issues and code quality problems, then apply optimizations directly to code. Use when user asks to analyze performance, audit code quality, find bottlenecks, reduce bundle size, optimize images/assets, remove duplicated code, or "make the code faster/cleaner/lighter" — even if not named explicitly. Trigger on "check the performance of this project", "optimize my codebase", "find and fix inefficiencies", "reduce bundle size", "clean up duplicated code".
- Repository
- web-dev-agent ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze codebase for performance issues and code quality problems, then apply optimizations directly to code. Use when user asks to analyze performance, audit code quality, find bottlenecks, reduce bundle size, optimize images/assets, remove duplicated code, or "make the code faster/cleaner/lighter" — even if not named explicitly. Trigger on "check the performance of this project", "optimize my codebase", "find and fix inefficiencies", "reduce bundle size", "clean up duplicated code".
Triggers from the description
Original author description
Analyze codebase for performance issues and code quality problems, then apply optimizations directly to code. Use when user asks to analyze performance, audit code quality, find bottlenecks, reduce bundle size, optimize images/assets, remove duplicated code, or "make the code faster/cleaner/lighter" — even if not named explicitly. Trigger on "check the performance of this project", "optimize my codebase", "find and fix inefficiencies", "reduce bundle size", "clean up duplicated code".
How it works
- Phase 1 — Analyze
- Phase 2 — Optimize
- Rules
SKILL.md preview
--- name: performance-optimizer description: Analyze codebase for performance issues and code quality problems, then apply optimizations directly to code. Use when user asks to analyze performance, audit code quality, find bottlenecks, reduce bundle size, optimize images/assets, remove duplicated code, or "make the code faster/cleaner/lighter" — even if not named explicitly. Trigger on "check the performance of this project", "optimize my codebase", "find and fix inefficiencies", "reduce bundle size", "clean up duplicated code". --- # Codebase Performance Optimizer Two phases: **Analyze** then **Optimize**. Always show findings before touching code, unless user says "just fix it". ## Phase 1 — Analyze 1. Map project: language(s), framework, build tool, package manager. `view` root dir, then relevant configs (package.json, webpack/vite config, tsconfig, etc). 2. Scan issue categories (grep/find via shell, or language-specific tools when available): - **Duplication**: repeated logic/blocks across files (near-identical functions, copy-pasted components). - **Bundle size**: heavy/unused deps, missing tree-shaking, no code-splitting, large barrel imports. - **Images/assets**: uncompressed images, wrong format (PNG where WebP/AVIF fits), oversized dimensions, missing lazy-loading. - **Runtime perf**: N+1 queries, unnecessary re-renders (React: missing memo/useMemo/useCallback, inline object/function props), blocking sync I/O, unindexed DB queries, O(n²) loops on large data. - **Dead code**: unused exports, unreachable branches, commented-out blocks. - **Build config**: missing minification, no compression (gzip/brotli), dev-only code shipped to prod. 3. Produce findings report (chat, concise): per issue — file:line, issue, impact (high/medium/low), proposed fix. 4. Ask user which categories to act on if list long, unless already said "fix everything". ## Phase 2 — Optimize Apply fixes incrementally, one category at a time, so changes stay reviewable: - **Dedup**: extract shared logic into function/module/component; update call sites. - **Bundle**: replace heavy deps with lighter alternatives (only if drop-in compatible), add/adjust code-splitting or dynamic imports, fix barrel-import issues. - **Images**: recompress/convert via shell (`cwebp`, `sharp`, `imagemin` if available — check what's installed first), resize to actual display dimensions, add lazy-loading attributes. - **Runtime**: memoization, batch queries, replace O(n²) with efficient structures/algorithms. - **Dead code**: remove after confirming no external references (grep whole repo first). After each category: run existing tests/build if project has them (`npm test`, `npm run build`, etc.) to confirm nothing broke. Report changes + why, file by file, short summary — not just "done". ## Rules - Never guess at "optimized" behavior that changes program output — perf fixes must be behavior-preserving. - Don't install new deps for a fix if native/existing solution works. - No test suite → flag it, proceed more conservatively (smaller diffs, manual reasoning about correctness). - Very large repos → sample representative files/modules first, not blind full scan; ask user for subfolder if scope unclear.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Domenico-Tenace-Open-Labs/web-dev-agent | 90 | MIT |
| smicolon/ai-kit | 100 | MIT |
| armanzeroeight/fastagent-plugins | 100 | MIT |
| armanzeroeight/fastagent-plugins | 100 | MIT |
| JochenYang/Jochen-ai-rules | 90 | MIT |
| 420company/artemis | 86 | MIT |
Database snapshot: 13.11.2026 · package version 15e37f9d75f7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90perf-audit
Audit frontend bundle size and Core Web Vitals risks. Use when asked to "audit performance", "analyze bundle", "check bundle size", "check Core Web Vitals", or find frontend bottlenecks. Don't use for backend performance, database queries, or diagnosing a specific slowdown (/debug). - 90code-review
Code review for quality, security, performance, and architecture. Use when reviewing code, auditing OWASP, checking SOLID, or finding perf bottlenecks and test gaps. - 84review-code
Review code changes for quality, security, and performance. Use when user says "review my changes", "do a code review", "check this for issues", "analyze code quality", "security review", "performance review", "is this PR ready", or needs architecture, security, performance, and style analysis. - 100optimization
Optimize code for performance and efficiency while preserving behavior. Use for "optimize", "make faster", "reduce memory", "performance". - 100audit-bundle-size
Analyse and shrink a web app's JavaScript bundle. Use when "reduce bundle size", "code splitting", "slow initial load", or "why is the bundle so big". Runtime → audit-performance. - 100prism-audit
Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".