Performance Review
Performance and resource-efficiency review of an open-source pull request or diff. Use when the diff introduces I/O inside a loop, new database queries or query predicates, caching or invalidation changes, large allocations or whole-file reads, changes to a documented hot path, an algorithmic complexity change, a switch between streaming and buffering, or a mix of blocking and async code. Applies a measurement-first rule — every claim must be backed by a benchmark run on both base and head, except complexity-class regressions and unbounded resource growth, which are arguable from the diff alon
Install
/plugin marketplace add priyank766/OpenSource-SKILLThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add priyank766/OpenSource-SKILL --skill performance-reviewgit clone --depth 1 https://github.com/priyank766/OpenSource-SKILL.git /tmp/OpenSource-SKILL
mkdir -p ~/.claude/skills
cp -r /tmp/OpenSource-SKILL/skills/performance-review ~/.claude/skills/performance-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Performance Review A specialised lens on top of [`pr-review`](https://github.com/priyank766/OpenSource-SKILL/blob/main/skills/pr-review/SKILL.md). Run that procedure first; this one replaces the line-by-line audit with a measurement discipline. **Read first:** [`DETECTION-PLAYBOOK.md`](references/DETECTION-PLAYBOOK.md) · [`QUALITY-FILTER.md`](references/QUALITY-FILTER.md) · [`REVIEW-VOICE.md`](references/REVIEW-VOICE.md) > **Where the time goes.** Finding the flaw is the review. The playbook above is the > general flaw-hunting procedure; this file is the domain-specific lens on top of it. > Scoring and writing the comment are the last ten minutes, not the work. **Severity floor: 8.0.** Comment budget: one per ~200 changed lines, max 5. --- ## The governing rule: no measurement, no comment An unmeasured performance suggestion cannot score above 6.0, because you cannot claim Correctness on a number you did not produce. Under the shared filter that is a silent reject. This is not a stylistic preference — it is the spine of the whole skill. | Claim | Evidence required | Without it | | :--- | :--- | :--- | | "This is slow" | base vs head timing, n runs, variance | reject | | "This allocates too much" | peak RSS or heap profile, both sides | reject | | "This would be faster as X" | X implemented and benchmarked | reject | | "This is O(n²) on a hot path" | the loop nesting in the diff + a call-graph path | **arguable** |
Details
- Skill name
performance-review- Repository
- priyank766/OpenSource-SKILL
- Path
skills/performance-review/SKILL.md- License
- Apache-2.0
- Repo updated
- 6 August 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Performance Review skill do?
Performance and resource-efficiency review of an open-source pull request or diff. Use when the diff introduces I/O inside a loop, new database queries or query predicates, caching or invalidation changes, large allocations or whole-file reads, changes to a documented hot path, an algorithmic complexity change, a switch between streaming and buffering, or a mix of blocking and async code. Applies a measurement-first rule — every claim must be backed by a benchmark run on both base and head, except complexity-class regressions and unbounded resource growth, which are arguable from the diff alon
How do I install the Performance Review skill?
Claude Code plugin: /plugin marketplace add priyank766/OpenSource-SKILL. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Performance Review popular?
It lives in priyank766/OpenSource-SKILL, which has 1 GitHub stars and 0 forks, and is included in 1 curated skill list.
Related skills
API Compat Review
1priyank766/OpenSource-SKILL
Backward-compatibility review of changes to a project's public surface. Use when a diff changes exported function or type signatures, renames or removes public symbols, changes a default value, alters config keys, environment variables, or CLI flags, modifies an HTTP or wire format, migrates a database schema, changes exception or error types, touches plugin or extension hooks, or whenever a PR proposes a major-version bump. Establishes what the project actually promises, diffs the public surface between base and head with language-native tooling, classifies each change against a breaking-chan
Contributor Experience Review
1priyank766/OpenSource-SKILL
Review of a first-time or early-stage contributor's pull request, where the technical bar stays fixed but the sequencing, batching, and supplied context change. Use when GitHub labels the author a first-time contributor, when the PR comes from a newcomer to this repo, when it arrives via Hacktoberfest, GSoC, Outreachy, or a good-first-issue, when the change is technically close but procedurally messy (missing DCO, wrong base branch, unsigned commits, failing lint), or when the PR must be declined and the decline needs to not cost the project a future contributor. Applies a raised severity floo
Dependency Review
1priyank766/OpenSource-SKILL
Supply-chain review of dependency and CI changes in an open-source pull request. Use when a PR adds or bumps a dependency, changes a lockfile, introduces a build or postinstall script, edits a GitHub Actions workflow, changes a container base image, or when a bot-generated dependency bump needs human judgement before merge. Covers install-time code execution, package-identity and typosquat checks, artifact provenance, transitive footprint, license class, and workflow privilege changes. Ecosystem-agnostic — npm, PyPI, Go, Cargo, RubyGems, Composer, containers. Do NOT use for routine patch bumps
PR Review
1priyank766/OpenSource-SKILL
High-signal, maintainer-grade review of an open-source pull request. Use when asked to review a PR, review a diff, look over changes before posting feedback, or when preparing review comments for a GitHub pull request. Applies a weighted 10-point quality filter so only findings scoring 8.0+ are surfaced, and enforces a human contributor voice instead of AI cheerleading. Works for any language or ecosystem. Do NOT use for reviewing your own uncommitted work-in-progress.
Commit
5lucaspmarie-a11y/claude-skills-vault
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
Comprehensive Review PR Enhance
5lucaspmarie-a11y/claude-skills-vault
Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.