Contributor Experience Review
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
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 contributor-experience-reviewgit clone --depth 1 https://github.com/priyank766/OpenSource-SKILL.git /tmp/OpenSource-SKILL
mkdir -p ~/.claude/skills
cp -r /tmp/OpenSource-SKILL/skills/contributor-experience-review ~/.claude/skills/contributor-experience-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Contributor Experience Review A sequencing lens on top of [`pr-review`](https://github.com/priyank766/OpenSource-SKILL/blob/main/skills/pr-review/SKILL.md), for PRs from people who have not contributed to this repo before. **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.5** — higher than the general floor of 8.0, not lower. A regular contributor reads a 7.5/10 nit as a nit and ignores it. A newcomer cannot tell a blocking issue from a preference, so every comment you post reads as a condition of merge, and a review of twelve comments reads as a rejection. The floor goes up because the cost of noise goes up. Cut harder, not softer. --- ## Governing rules **The bar is the same.** Correctness, tests, scope, and API compatibility are judged exactly as they would be for a core maintainer. Merging a weaker patch because the author is new ships a bug to users, leaves the maintainer holding it, and teaches the contributor that this project does not mean what it says. Only the *sequencing* changes.
Details
- Skill name
contributor-experience-review- Repository
- priyank766/OpenSource-SKILL
- Path
skills/contributor-experience-review/SKILL.md- License
- Apache-2.0
- Repo updated
- 6 August 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Contributor Experience Review skill do?
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
How do I install the Contributor Experience 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 Contributor Experience 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
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
Docs Review
1priyank766/OpenSource-SKILL
Review of documentation correctness in an open-source pull request — treating docs as unexecuted code and verifying them by running them. Use when a diff touches README files, docstrings, tutorials, quickstarts, API reference, migration guides, changelogs, or example projects, and equally when a code diff renames a symbol, changes a default, adds a required argument, or alters a config key in a way that silently invalidates documentation elsewhere in the repo. Verifies samples in a clean environment, walks quickstarts from an empty state, greps the docs tree for every symbol the diff touched,
Triage Issues
5TalonT-Org/AutoSkillit
Analyze open GitHub issues and produce a sequenced implementation plan — grouping issues into parallel batches, ordering those batches, and tagging each issue with its recipe route. Use when user says "triage issues", "prioritize issues", or "plan issue order".
Performance Review
1priyank766/OpenSource-SKILL
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
Run Experiment
5TalonT-Org/AutoSkillit
Execute a designed experiment in a worktree and collect structured results. Supports --adjust retry mode.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.