performance-review
Review code changes for performance anti-patterns — N+1 queries, unbounded results, blocking ops.
Works with
--- name: performance-review description: Review code changes for performance anti-patterns — N+1 queries, unbounded results, blocking ops. license: MIT --- # /performance-review Spawns the `performance-reviewer` agent to detect performance anti-patterns in your code changes. ## Steps 1. **Gather context** — detect the scope of changes to review: - If arguments are provided (file paths or PR number), use those as scope - Otherwise, use `git diff` to determine what changed - Identify files touching database queries, API endpoints, or data processing 2. **Spawn the agent** — use the Task tool: ``` Task tool with subagent_type="performance-reviewer" ``` Pass in the prompt: - The diff output and list of changed files - The project's database ORM and framework context - Any performance budgets or constraints from project rules 3. **Present findings** — relay the agent's performance report: - Group by severity: CRITICAL > WARNING - Include specific code locations and estimated impact - Show recommended fixes with before/after examples 4. **Offer follow-up actions**: - "Fix critical issues?" — apply recommended performance fixes - "Add benchmarks?" — create performance tests for flagged code paths - "Review again?" — re-run after changes
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.
