optimize

Audit code changes for cleanup issues or benchmark gaps against best practices.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Suge8/skills --skill optimize-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: optimize
Source: https://github.com/Suge8/skills/tree/main/development/optimize
Command: npx skills add https://github.com/Suge8/skills --skill optimize-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open-ended questions like "is there room for optimization" never terminate because a model can always invent new work. This Skill splits optimization audits into two bounded branches—a closed cleanup checklist and an externally-anchored benchmarking review—so audits have objective stopping criteria. ## Core Features & Use Cases - Closeout (subtractive) audit: Scans a fixed 7-item checklist (dead code, multiple sources of truth, split implementations, defensive patches, polling, magic values, vague naming) over the current Git diff scope, producing P0/P1/P2 findings with evidence, impact, fix, and verification steps. - Elevate (additive) audit: Researches official docs, competitor source code, and industry reports via web search to find cited gaps between your implementation and current best practices, ranked by benefit and cost. - Use Case: Before merging a feature branch, ask whether the diff is clean; the Skill reports scoped findings with file and line evidence, or explicitly concludes "audit passed, no closeout points" instead of inventing work. ## Quick Start Ask the agent to audit the current Git diff for cleanup issues before merging, or to compare a module against industry best practices.

Frequently Asked Questions about optimize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Git diff for dead code before merging?▼

Run the closeout branch, which scans the current diff scope against a fixed 7-item checklist covering dead code, duplicate logic, and defensive patches. Each finding includes file, line, evidence, impact, and a verification step.

How to compare my code against industry best practices?▼

Use the elevate branch, which researches official documentation, competitor source code, and industry reports via web search. Every improvement opportunity must cite a source and includes benefit, cost, and a do-or-skip recommendation.

What is the difference between the closeout and elevate branches?▼

Closeout is subtractive: it checks whether current changes are clean using a bounded checklist with a defined endpoint. Elevate is additive: it finds gaps versus external best practices, anchored to cited sources rather than invented ideas.

Does the audit modify code automatically?▼

No. The Skill reports findings first and only fixes items the user selects. After fixes, it re-scans only the modified items and their direct impact area rather than restarting a full audit.

When should I not use this optimization audit?▼

Avoid it for full-repository architecture reviews, which belong to dedicated architecture skills, and for speculative future-proofing refactors. The audit explicitly rejects YAGNI violations and findings without concrete file and line evidence.