dependency-upgrade
Skill0 starsChanged 24 days agoMITView on GitHub
Safely upgrade a specified package or small dependency group, inspect supply-chain changes, and verify compatibility. Use for targeted version updates; not automatic bulk maintenance.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- HyperVon/agent-guidance-kittheir own version, first seen Nov 1, 2026
- navikt/copilottheir own version, first seen Nov 1, 2026
- agentkitco/agentkit-dev-skillstheir own version, first seen Nov 1, 2026
- Eliahhango/nullbyte-securitytheir own version, first seen Nov 1, 2026
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
Used with
Projects with it also use incident-response, code-review and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillincident-response
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 6 projects that use this
- GoogleSkill
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
- +1 more from google
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- secondsky/sap-skills★ 462same name
- navikt/copilot★ 61same name
- xfstudio/skills★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- Eliahhango/nullbyte-security★ 4same name
- juanitourquiza/shipframe★ 4same name
- WST2002/claude-code-skills★ 4same name
- 0disoft/mcp-security-proxy★ 2same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-qaSkill
- architecture-reviewSkill
- bug-fix-verificationSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- migration-safetySkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- root-cause-investigationSkill
- security-reviewSkill
- surgical-changeSkill
- test-gap-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Read official changelog/release notes and security advisories when available.
- Distinctive: line 14
Run targeted build, tests, and critical integration checks.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency upgrade
Upgrade for a reason. Avoid turning one package bump into a lockfile rewrite of the world.
- Confirm requested packages, target version policy, package manager, supported runtimes, and the real dependency manifest and lockfile.
- Read official changelog/release notes and security advisories when available. If sources are unavailable, state the limitation and avoid invented migration instructions.
- Compare compatibility: major-version breaks, transitive movement, peer requirements, native toolchains, license changes, build scripts, and package provenance when relevant.
- Establish baseline verification. Update only scoped manifests and the required lockfile using the project's existing tooling; do not disable checks or ignore unrelated lockfile churn.
- Run targeted build, tests, and critical integration checks. Inspect exact manifest/lockfile changes and unexpected new packages or install scripts.
- Report observed version changes, residual risks, and any follow-up migration. Stop for suspicious provenance, unexpected script execution requirements, or a broad unexplained dependency graph rewrite.
Boundaries
Package installation may run third-party scripts or contact a registry. Honor the sandbox and authorization rules; explain when verification cannot be done safely. Never publish packages or change CI credentials as part of a version bump.
Output
Before/after versions, reason, scope, compatibility changes, checks, unexpected transitive changes, remaining risks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.