From codex-next
Diagnoses slow code, APIs, queries, memory growth, frontend load, build regressions, and scalability limits using a structured measurement-based workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codex-next:dev-performance-diagnosisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this workflow when there is a measurable performance problem or performance-sensitive change.
Use this workflow when there is a measurable performance problem or performance-sensitive change.
Define the metric.
Establish a baseline.
Form hypotheses.
Test one change at a time.
Confirm no regression.
Return:
npx claudepluginhub blueskyxn/codex-is-all-you-need --plugin codex-nextDiagnoses frontend and backend performance bottlenecks including bundle size, N+1 queries, memory leaks, and Core Web Vitals. Prioritizes fixes by impact.
Analyzes performance bottlenecks in web pages, APIs, builds and delivers prioritized fixes with baselines from Lighthouse, Chrome DevTools, cProfile, py-spy, clinic.js, EXPLAIN ANALYZE.
Profiles system performance to identify bottlenecks using measurement before optimization — follows Brendan Gregg's USE Method and Google pprof methodology.