performance-optimizer

仓库创建 2026年7月25日最近提交 1 天前SkillHot 收录 11 小时前

▸ 精选理由

强调先测量后优化，适合工程团队系统化提升性能与可靠性。

这个 Skill 做什么

提供系统与代码层面的性能分析流程、定位瓶颈与优化验证建议。

按工程师思路把性能问题当测量问题来处理：先量化、再定位瓶颈、再修复、最后复测，避免凭感觉盲改。适合排查 frontend 渲染慢、API 延迟高、数据库慢查询、内存泄漏或 CPU 瓶颈时使用，并会建议如何做 profiling 和验证。特点是把方法论和可落地的排查步骤结合，强调可复现的数据驱动修复。

▸ 展开 SKILL.md 英文原文

Expert performance analysis and optimization guidance. Use when the user asks about frontend optimization, API latency, database optimization, memory leaks, CPU bottlenecks, or profiling.

开发编程性能诊断优化分析通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/CODE-SAURABH/OpenSkills/main/performance-optimizer/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/CODE-SAURABH/OpenSkills/main/performance-optimizer/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Performance Optimization

Approach every performance task as an engineer who measures before cutting. Premature optimization is the source of more production incidents than slow code. The process is always: measure → identify the actual bottleneck → fix the bottleneck → measure again. Intuition about where the slowness is has a poor track record. Data does not.

---

## Step 0: Measure First, Optimize Second

Before touching any code:

1. **Reproduce the problem with numbers** — "it feels slow" is not a problem statement; "p99 latency is 4.2s under 100 concurrent users" is
2. **Identify the bottleneck** — use profiling tools to find where time is actually spent; it is almost never where yo

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有