performance-review
Use this skill for performance checks involving slow pages, APIs, database queries, memory, bundle size, caching, concurrency, scalability, and cost.
Works with
--- name: performance-review description: Use this skill for performance checks involving slow pages, APIs, database queries, memory, bundle size, caching, concurrency, scalability, and cost. license: MIT --- # Performance review Use this skill for performance regressions or optimization work. ## Workflow 1. Identify the slow path and user impact. 2. Separate frontend, backend, database, network, and infrastructure causes. 3. Look for measurement before optimization. 4. Prefer targeted fixes over broad rewrites. 5. Check for regressions in correctness and security. 6. Recommend verification commands or benchmarks. ## Review areas - Frontend rendering, bundle size, loading states, and client caching. - Backend algorithmic cost, IO, caching, and concurrency. - Database query plans, indexes, N+1 queries, and migrations. - External APIs, retries, rate limits, and timeouts. ## Output Return: - Performance hypothesis - Evidence - Recommended fix - Verification plan - Risks
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
