---
name: dependency-maintenance
description: 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.
title: dependency-maintenance
canonical_url: https://skilld.dev/gh/pingdotgg/t3code/dependency-maintenance
last_updated: 2026-11-12T14:20:12.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [coordinated-upgrades.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/dependency-maintenance/coordinated-upgrades.md), [manifest-roles.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/dependency-maintenance/manifest-roles.md).
>
> If the user asked to install this Skill, run `npx skilld install pingdotgg/t3code/dependency-maintenance`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/dependency-maintenance`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/pingdotgg/t3code/dependency-maintenance) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/dependency-maintenance`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/dependency-maintenance --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/dependency-maintenance --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

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](https://skilld.dev/api/skills-raw/pingdotgg/t3code/dependency-maintenance/manifest-roles.md) before selecting its role.
5. Select the package-local or coordinated branch and its validation matrix.

Discovery is complete when every match and affected validation surface is
accounted for.

## Package-local branch

Use this branch only for one dependency in one workspace package when runtime,
compiler, package-manager, image, patch, native-build, and shared-tooling policy
are unchanged.

Update only the owning manifest and keep peer compatibility independent from
the development version tested here. If any coordinated surface appears,
switch branches.

This branch is complete when the manifest and lockfile agree, focused checks
pass, and every search result is intentionally unchanged or package-local.

## Coordinated branch

Read [coordinated-upgrades.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/dependency-maintenance/coordinated-upgrades.md), select every applicable
row, and update all listed synchronization points before installing. Apply root
workflow and generated-file requirements before editing those surfaces, then
return here to finish matrix and lockfile review.

## Install and finish

Run root `pnpm install` after all selected edits. Inspect warnings and the
semantic lockfile diff for specifiers, resolutions, duplicate transitives, peer
changes, integrity, patch hashes, lifecycle scripts, and `allowBuilds` effects.
A successful install alone does not complete this review.

Run the narrowest correctness and performance checks that cover every selected
matrix row.
Apply the root changeset routing after implementation and focused validation.

The task is complete when repeated repository searches find no unclassified
synchronization point, manifest roles and compatibility ranges are intentional,
the lockfile has no unexplained churn, and every selected check passes or is
reported as not runnable.
