dependency-care
Skill0 starsChanged 13 days agoMITView on GitHub
Evaluate dependency updates and vulnerabilities without creating avoidable breakage. Use when upgrading packages, responding to advisories, or cleaning dependency drift.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- build-rescueSkill
- change-narrativeSkill
- context-handoffSkill
- data-quality-gateSkill
- dataset-workshopSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- model-eval-designSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- release-readinessSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- safe-migrationSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- could be automatic: a setting could enforce it
- Distinctive: line 13
Prefer the smallest version change that resolves the stated problem.
- Distinctive: line 14
Update manifests and lockfiles through the repository's package manager.
- Distinctive: line 15
Run install in the intended mode, relevant tests, type checking, build, and any package-specific smoke test.
- Distinctive: line 19
Do not run untrusted install scripts, elevate permissions, or point package managers at unknown registries without explicit approval.
- Distinctive: line 20
Do not automatically upgrade every package to latest just because an audit command reports updates.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency Care
Procedure
- Identify package manager, lockfile, supported runtime versions, direct versus transitive dependencies, and existing update policy.
- Determine the reason for the update: security fix, bug fix, feature, compatibility, or maintenance. Find authoritative release notes and advisory details when network access is available.
- Inspect semver impact, deprecations, peer constraints, native modules, license changes, and minimum runtime requirements.
- Prefer the smallest version change that resolves the stated problem. Do not combine unrelated dependency churn with application changes.
- Update manifests and lockfiles through the repository's package manager; never hand-edit generated lock data unless the project explicitly requires it.
- Run install in the intended mode, relevant tests, type checking, build, and any package-specific smoke test.
- Summarize packages changed, reason, behavior changes, compatibility concerns, and verification outcomes.
Boundaries
- Do not run untrusted install scripts, elevate permissions, or point package managers at unknown registries without explicit approval.
- Do not automatically upgrade every package to latest just because an audit command reports updates.
- A clean vulnerability scan does not prove a dependency set is risk-free; disclose tool and database limits.
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.