Skip to content

tobihagemann/turbo / codex/skills/review-dependencies

review-dependencies

Verified

Find outdated or vulnerable dependencies and GitHub Actions pins without upgrading them. Use when the user asks to "review dependencies", "check for outdated packages", or "scan dependencies".

Review Dependencies

Detect package managers and CI action pins, then discover outdated or vulnerable dependencies. Analysis only. Does not upgrade.

Step 1: Detect Package Managers

Identify which package managers are in use by searching for config files:

Config filePackage managerLockfileEcosystem
package.jsonnpm / yarn / pnpmpackage-lock.json / yarn.lock / pnpm-lock.yamlNode.js
Package.swift, *.xcodeprojSwift Package ManagerPackage.resolvedSwift
pyproject.toml, requirements.txt, setup.pypip / poetry / uvpoetry.lock, uv.lockPython
Cargo.tomlcargoCargo.lockRust
go.modGo modulesgo.sumGo
GemfileBundlerGemfile.lockRuby
pom.xmlMaven—Java
build.gradle, build.gradle.ktsGradlegradle.lockfileJava/Kotlin
.github/workflows/*.yml / .yaml, action.yml / .yamlGitHub Actions—CI

Swift dependencies can live in Package.swift or be configured directly in the Xcode project file (.xcodeproj/.xcworkspace). For Xcode-managed dependencies, inspect the project's package references.

Detection steps:

  1. Search for config files in the project root and subdirectories (exclude vendored directories)
  2. If a lockfile exists, use the corresponding package manager variant (e.g., yarn.lock → yarn, pnpm-lock.yaml → pnpm)
  3. When the repo declares a dependency automation config (.github/dependabot.yml / .yaml, renovate.json, .github/renovate.json), read it and add every ecosystem it declares to the set found by the config-file search
  4. When the repo has a GitHub remote, list open dependency PRs with gh pr list --author app/dependabot (or app/renovate), and mark each upgrade one of them already proposes
  5. If multiple instances of the same package manager found (e.g., monorepo with several package.json files): use request_user_input to let the user pick one (Codex request_user_input choices are mutually exclusive). For an "all of them" workflow, ask follow-up free-form input or run the review per instance.
  6. If multiple package managers found: use request_user_input to let the user pick one. Exclude the CI ecosystem from that choice and review it alongside whichever the user picks
  7. If none found across every step above: inform user and stop

Step 2: Discovery

Run the appropriate discovery command to find available updates:

Package managerDiscovery commandNotes
npmncu --format groupRequires npm-check-updates. Suggest npm install -g npm-check-updates if missing.
yarnncu --format group or yarn upgrade-interactive
pnpmncu --format group or pnpm outdated
Swift PMCheck resolved versions in Package.resolved against latest releases via web searchNo built-in outdated command. Read Package.swift or inspect the Xcode project to identify dependencies and their current version constraints.
pippip list --outdated
poetrypoetry show --outdated
uvuv pip list --outdated
cargocargo outdatedRequires cargo-outdated. Fall back to comparing Cargo.toml versions via web search.
Go modulesgo list -m -u all
Bundlerbundle outdated
Mavenmvn versions:display-dependency-updates
Gradlegradle dependencyUpdatesRequires com.github.ben-manes.versions plugin.
GitHub Actionsgh api repos/<owner>/<repo>/releases/latest --jq .tag_name, compared against each uses: refNo outdated command. Take <owner>/<repo> from the ref's first two path segments. Read a SHA-pinned ref's version from its trailing comment (uses: <owner>/<action>@<sha> # v1.2.3). Compare only the components the ref pins, so @v7 is current against v7.0.1. Fall back to repos/<owner>/<repo>/tags when the release 404s or its tag namespace differs from the ref's, and to web search when the action is not hosted on GitHub. Exclude local (./…), <repo-relative> ($/…), and Docker (docker://…) refs, which pin no release.

Also check for an update to the version pin the project declares for the package manager itself, such as packageManager or devEngines.packageManager in package.json or the Gradle wrapper's distribution version, when the discovery command leaves it out.

When the package manager or the repo's dependency automation (Dependabot cooldown, Renovate minimumReleaseAge) enforces a minimum release age, propose only versions the guard admits, naming the newest admitted version as the target. Hold a release that fixes a known vulnerability in the current version only to a guard the package manager enforces, and run discovery with a matching cooldown only for such a guard, where the tool has one (ncu --cooldown <days>).

Categorize updates:

  • Major (breaking changes) — requires migration research
  • Minor (new features, backward compatible)
  • Patch (bug fixes)

Step 3: Report Findings

If the discovery tool is not installed, suggest the installation command (see Step 2 notes column). If no tool exists for the ecosystem, fall back to manual version checking via web search.

If no updates are available, report that dependencies are up to date. Otherwise, report each update in the output format below, followed by the Overall Verdict.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

Output Format

Format each finding as:

### [P<N>] <title (imperative, <=80 chars)>

**Package:** `<name>` <current> -> <target>
**Manager:** <npm/pip/cargo/etc.>
**Proposed:** <open automation PR already covering this upgrade, when one exists>

<one paragraph: why this matters, known vulnerabilities if any, major version gap>

After all findings, add:

## Overall Verdict

**Dependencies:** <up to date | updates available>

<summary with counts: N major, N minor, N patch>

Priority Levels

  • P0 — Known security vulnerability (CVE) in the current version
  • P1 — Multiple major versions behind (e.g., React 17 → 19)
  • P2 — One major version behind or significantly outdated minor versions
  • P3 — Minor or patch updates available
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall