Dependency Review
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
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 dependency-reviewgit clone --depth 1 https://github.com/priyank766/OpenSource-SKILL.git /tmp/OpenSource-SKILL
mkdir -p ~/.claude/skills
cp -r /tmp/OpenSource-SKILL/skills/dependency-review ~/.claude/skills/dependency-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Dependency & Supply-Chain Review The lens for PRs where the risk is not in the diff's own code but in the code the diff invites in. Layered on top of [`pr-review`](https://github.com/priyank766/OpenSource-SKILL/blob/main/skills/pr-review/SKILL.md). **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: 7.5** — lower than the suite default of 8.0. A malicious or compromised dependency executes with full build and runtime privilege on every contributor's laptop and inside CI, where the tokens live. A false positive costs one thread of discussion. A miss costs the project's release signing key. That asymmetry justifies the lower bar; it does not justify posting health-score trivia. --- ## The governing rule > Adding a dependency adds every one of that package's maintainers to your project's trust > boundary — and every maintainer of every one of its transitive dependencies too. So the review question is never "is this library good". It is: **What does merging this let someone else execute, and where?** "Where" has three answers, in descending order of severity: in CI with repository
Details
- Skill name
dependency-review- Repository
- priyank766/OpenSource-SKILL
- Path
skills/dependency-review/SKILL.md- License
- Apache-2.0
- Repo updated
- 6 August 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Dependency Review skill do?
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
How do I install the Dependency 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 Dependency 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
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,
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
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.
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".
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.