dependency-updater
Scan a project's package manifests across ecosystems (Python, JavaScript/npm, Rust, Go) for outdated dependencies, detect version conflicts across a monorepo, and propose updates with explicit confirmation before applying any change. Use when checking for outdated dependencies, planning a dependency bump, auditing dependency freshness, or asked to update packages across a repo or monorepo. Not for working through dependabot pull requests that are already open (merge, close or rebase them) — that is `triaging-dependabot-prs`; this skill scans and edits the local checkout's manifests and never touches PRs.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- dependency-updater
- description
- Scan a project's package manifests across ecosystems (Python, JavaScript/npm, Rust, Go) for outdated dependencies, detect version conflicts across a monorepo, and propose updates with explicit confirmation before applying any change. Use when checking for outdated dependencies, planning a dependency bump, auditing dependency freshness, or asked to update packages across a repo or monorepo. Not for working through dependabot pull requests that are already open (merge, close or rebase them) — that is `triaging-dependabot-prs`; this skill scans and edits the local checkout's manifests and never touches PRs.
- allowed-tools
- Glob, Read, Edit, Bash(uv pip list:*), Bash(uv lock:*), Bash(pip list:*), Bash(pip-audit:*), Bash(npm outdated:*), Bash(npm audit:*), Bash(npm install:*), Bash(cargo outdated:*), Bash(cargo update:*), Bash(go list:*), Bash(go mod tidy:*), Bash(git diff:*), Bash(git status:*)
02 资源文件 1
- 脚本scripts/smoke_test.py7.8 KB
03 SKILL.md 正文
Dependency Updater
Discover a project's package manifests, check each ecosystem for outdated dependencies, flag version conflicts across a monorepo, and propose specific updates — never applying anything without confirmation.
This skill has no dependency on any other plugin. The optional security-advisory step (step 5) is self-contained: it only runs an ecosystem's own advisory tool if one is available, and is skipped entirely otherwise.
Quick Start
- Find every package manifest in the repo (step 1) and check each ecosystem for outdated dependencies (step 2).
- Present the findings grouped by ecosystem, with major bumps and cross-manifest conflicts called out (steps 3-6).
- Ask which updates to apply (step 7); edit the manifests only for what was approved (step 8), and ask again before regenerating any lockfile (step 9).
When to Use
Checking for outdated dependencies, planning a dependency bump, auditing dependency freshness, or updating packages across a repo or monorepo from its local manifests. For dependabot pull requests that are already open, use triaging-dependabot-prs instead (see "When NOT to Use").
Instructions
- Discover manifests: use
Globto find package manifests across the repo, including nested workspace members (e.g.**/pyproject.toml,**/requirements*.txt,**/package.json,**/Cargo.toml,**/go.mod). In a monorepo, a manifest can exist at the root and again under each package/plugin directory — collect all of them, not just the first match. - Check each ecosystem found for outdated dependencies:
- Python:
uv pip list --outdatedif the project usesuv(auv.lockis present), otherwisepip list --outdated - JavaScript/npm:
npm outdated - Rust:
cargo outdated(if thecargo-outdatedsubcommand isn't installed, note that and skip — don't fail the whole scan over one missing tool) - Go:
go list -u -m all
- Python:
- Build a per-ecosystem table: package, current version, latest version, and update type (patch/minor/major) inferred from semver.
- Detect version conflicts: within the same ecosystem, the same dependency pinned to different versions across manifests in the repo (common in monorepos where each package pins independently). Flag these separately from ordinary outdated-version findings — they need a compatible-version decision, not just a bump.
- Security advisories (optional): if the ecosystem has its own advisory tool readily available (e.g.
npm audit,pip-auditif installed), offer to run it and fold any findings into the table. Skip silently if no such tool is available — do not treat this as a failure, and do not reach for any external plugin or service to fill the gap. - Present findings: show the full table grouped by ecosystem, with major-version bumps and cross-manifest conflicts called out most prominently — those carry the highest risk of breaking changes.
- Confirm which updates to apply: use
AskUserQuestion— options should include at minimum "patch/minor only" (lower risk), "all including major" (higher risk), "let me pick specific packages," and "none, just report." Never apply an update the user hasn't approved. - Apply approved updates: edit each manifest's version pin directly (
Edit). Batch by ecosystem. - Regenerate lockfiles: for each ecosystem with edited manifests, ask for a second, separate confirmation before running the install/lock command (
npm install,uv lock,cargo update,go mod tidy) — this mutates lockfiles and can pull in transitive changes beyond what was approved in step 7, so it gets its own gate rather than riding along with step 7's approval. - Show the result: which files changed (
git status/git diff), old → new version per package actually applied. - Remind, don't run, tests: dependency bumps — especially major ones — can break builds or behavior. Tell the user to run their test suite before committing; don't run it automatically, since test commands vary per project and can be slow.
Monorepo Consistency
When the same dependency is bumped across multiple manifests in one pass, keep every occurrence on the same resolved version — don't leave some manifests updated and others on the old pin. If a conflict (step 4) can't be resolved to one compatible version across all manifests that need it, surface that explicitly rather than picking one silently.
When NOT to Use
What this skill does not do:
- Does not install new dependencies — it only updates versions of dependencies already present in a manifest.
- Does not migrate code for breaking API changes introduced by a major bump — it reports the bump, the user (or a separate coding pass) handles the migration.
- Does not run the project's test suite or CI checks.
- Does not merge, close or rebase open dependabot pull requests — that is
triaging-dependabot-prs. The criterion: a bump that already exists as an open PR goes there; a bump not yet proposed (found by scanning the local manifests) stays here. - Does not depend on any other plugin, agent, or hook — every step above uses only this repo's own manifests and each ecosystem's own CLI tooling.
Testing & Validation
Eval coverage: this skill has no eval suite (no evals.json). Its steps run each ecosystem's own CLI tooling (npm outdated, uv pip list, cargo outdated, go list) against a real manifest tree, which a simulated-agent eval cannot exercise faithfully. Its structure is checked by scripts/smoke_test.py (frontmatter, referenced files, Bash grants, step sequence), and the quality gates below are checked by re-reading the skill against any change.
Last dated run record: 2026-10-08 — scripts/smoke_test.py (4 structural checks) passes after the Quick Start, When to Use and When NOT to Use sections and the triaging-dependabot-prs exclusion were added. No earlier dated run is recorded, and there has been no live run of the manifest scan itself.
Verify this skill activates on:
- "check for outdated dependencies"
- "plan a dependency bump" / "update packages across the repo"
- "audit dependency freshness" / "are there any version conflicts across the monorepo"
Verify it does NOT activate on:
- "install this new package" → not this skill; it only updates versions already present in a manifest
- "migrate this code for the breaking changes in the new major version" → not this skill; it reports the bump, a separate coding pass handles the migration
- "run the test suite" → not this skill; it reminds the user to test but never runs tests itself
- "merge the open dependabot PRs" / "triage the dependabot PRs" →
triaging-dependabot-prs; this skill only scans local manifests and has no PR, CI or merge awareness
Quality gates:
- [ ] Step 1 collects every manifest match across the monorepo (root and nested package/plugin directories) — never stops at the first match
- [ ] Step 4's version conflicts are always flagged separately from ordinary outdated-version findings — never merged into the same table row
- [ ] Step 5's security-advisory check always skips silently when no advisory tool is available — never fails the whole scan over one missing tool
- [ ] Step 7 always gates on
AskUserQuestionbefore any manifest edit — no update is ever applied without explicit approval - [ ] Step 9's lockfile regeneration always asks a second, separate confirmation — never rides along with step 7's approval
- [ ] The Monorepo Consistency section's rule is honored: a dependency bumped across multiple manifests in one pass never ends up on mismatched versions, and an unresolvable conflict is always surfaced rather than resolved silently
- [ ] Step 11 never runs the project's test suite automatically — only reminds the user to run it
Reference Guide
| Resource | Purpose |
|---|---|
scripts/smoke_test.py |
Persisted structural smoke test — re-run after any SKILL.md edit |
04 同仓库更多 Skills
demo
Fixture skill used by scripts.marketplace_ci sync tests.
export-demo
Fixture skill used by scripts.marketplace_ci export tests.
work-to-development
Validate an accepted Linear Issue's readiness for implementation (criteria, dependencies, duplicate/existing artifacts) and request governed branch/worktree creation through git-kit:starting-work — recording work-started Git/GitHub evidence and a deliberate Linear Started transition only after Git identity is read back and verified. Use when asked to start work on a Linear issue, begin development for an accepted issue, or prepare an accepted issue for implementation. Never creates a branch directly — always delegates to git-kit.
work-linking
Create and maintain stable cross-system links and authority labels between Notion and Linear records, and detect/repair drift between them. Use when asked to link a Notion record to a Linear record, check for drift between Notion and Linear, or repair a broken/stale link. Repairs only the bounded non-authoritative copy or link — never chooses by newest timestamp, and never creates a reverse-write loop against either system's own authority.
status-and-learning
Produce a dated, explicitly non-live Linear-to-Notion progress summary, or capture an outcome/learning after work completes. Use when asked to summarize progress to Notion, report portfolio status, or capture what was learned from a completed piece of work — not to disposition open follow-up items (see open-item-management for that). Never runs automatically or continuously — every summary is a deliberate, approved snapshot, not a live sync.
repository-gates
Discover, delegate, record, and invalidate this repository's actual Git/GitHub lifecycle gates (pre-commit, pre-push, PR required checks, Codex delta review, review requirements, merge rights) and the repository-policy provider profile that maps governed operations to git-kit. Use when asked what gates apply to this repository, to discover repository policy before starting Wave 2 work, or to check whether prior gate evidence is still valid after new commits. Discovery and delegation only — never executes a gate's own internal logic, and never invents a gate the repository doesn't actually define (in particular, never assumes a "Review Changes" gate exists).