Individual skill
dependency-maintenance
Dependency maintenance. Use when adding, moving, or upgrading dependencies, changing pnpm or JavaScript runtimes, updating TypeScript or build/test tools, or changing native-build policy, patches, or test images.
repos/effect/.agents/skills/dependency-maintenance/SKILL.md
Source commit a471adb24d750ab9e8d8312edad53ff6f26d961b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,204
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,729 bytescoordinated-upgrades.mddoc · 2,577 bytesmanifest-roles.mddoc · 2,138 bytes
Read excerpt
Treat an upgrade as a synchronization task, not a lockfile refresh. Derive
versions, commands, and compatibility points from the current repository.
## Discover
1. Read affected manifests and scripts, `pnpm-workspace.yaml`, setup actions,
workflows, test configuration, and compatibility documentation.
2. Search for the dependency and every current version, range, runtime input,
image, engine constraint, patch, and compatibility claim.
3. Record each match as a development version, tested version, peer range,
engine minimum, advertised minimum, or intentionally different constraint.
4. When adding or moving a manifest entry, read
[manifest-roles.md](manifest-roles.md) before selecting its role.
5. Select the package-local or coordinated branch and its validation matrix.