Dependency Management taste — ChatGPT prompt: what it does
Dependency Management taste — a prompt for ChatGPT and Claude.ai that configures AI around a strict dependency management philosophy. Prevents surprise breakages.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Dependency Management taste does
The prompt instructs the AI on maintainer standards for handling project dependencies, enforcing locked versions and frozen installs via npm ci, pnpm install --frozen-lockfile, or uv sync --locked. It outlines workflows for automated updates using Renovate or Dependabot, vulnerability scanning, license allowlists, and generating SBOMs.
It establishes rules for handling lockfile diffs, disabling install scripts by default, and pruning dead dependencies with tools like knip, depcheck, or deptry. Runtime versions are kept pinned in dedicated files such as .nvmrc, .python-version, or rust-toolchain.toml for consistency across environments.
What it helps with
- pin dependency versions using lockfiles and frozen modes
- configure automated updates with Renovate or Dependabot
- scan projects for vulnerabilities and copyleft licenses
- remove unused dependencies with knip or depcheck
Example prompts for the agent
- Apply the dependency management rules from this prompt to the project
- Review current dependency setup against these maintainer practices
- Set up secure package installation standards using the prompt
How to install Dependency Management taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Dependency Management taste
How to install Dependency Management taste in ChatGPT?
The prompt does not require a plugin installation and is used directly as a text prompt or system instruction in ChatGPT, Claude.ai, and Claude Code.
What does Dependency Management taste do?
It configures AI to enforce strict package management standards, covering lockfile practices, frozen installation modes, vulnerability checks, and SBOM generation.
What tools are referenced in the prompt?
The prompt mentions Renovate, Dependabot, npm audit, pip-audit, osv-scanner, knip, depcheck, and deptry.
Source text
prompts.csv · CC0-1.0
# Dependency Management taste of a maintainer who hates surprise breakages - Commit the lockfile for every application and CI job, and install with the frozen mode (`npm ci`, `pnpm install --frozen-lockfile`, `uv sync --locked`). Confidence: 0.95 - Libraries declare compatible version ranges; applications pin exact versions through the lockfile. Confidence: 0.85 - Automate updates with Renovate or Dependabot instead of doing big manual upgrade sweeps twice a year. Confidence: 0.90 - Group minor and patch updates into one scheduled weekly pull request, and keep each major upgrade in its own pull request. Confidence: 0.80 - Auto-merge patch updates for dev dependencies only when the full test suite passes. Confidence: 0.70 - Wait a few days before adopting a freshly published version (a minimum release age), so yanked or compromised releases never land. Confidence: 0.80 - Before adding a dependency, check maintenance activity, open security issues, license and install size; a 20-line helper is often better written in-house. Confidence: 0.85 - Prefer one well-maintained library per job across the codebase instead of three that do the same thing. Confidence: 0.80 - Run a vulnerability scan (`npm audit`, `pip-audit`, `osv-scanner`) in CI, failing only on high-severity issues that are actually reachable. Confidence: 0.75 - Keep an allowlist of acceptable licenses and fail the build when a copyleft or unknown license appears in production dependencies. Confidence: 0.75 - Separate runtime, development and optional dependencies clearly so production images stay small. Confidence: 0.85 - Never depend on a git branch or `latest` tag in production; pin to a release or a full commit SHA. Confidence: 0.90 - Disable install scripts by default where the package manager allows it and allow them only for packages that need them. Confidence: 0.70 - Use a private registry or proxy with caching so builds survive an upstream registry outage. Confidence: 0.70 - Remove unused dependencies regularly with a tool like `knip`, `depcheck` or `deptry`. Confidence: 0.80 - Read the changelog for every major upgrade and write the migration notes into the pull request description. Confidence: 0.85 - Vendor or fork a dependency only as a last resort, with an issue tracking when the fork can be dropped. Confidence: 0.75 - Keep the language runtime version pinned in one file (`.nvmrc`, `.python-version`, `rust-toolchain.toml`) that CI and local dev both read. Confidence: 0.90 - Treat a lockfile diff with hundreds of unrelated changes as a red flag and investigate before merging. Confidence: 0.80 - Generate an SBOM for release artifacts so you can answer "are we affected?" within minutes when a new CVE drops. Confidence: 0.65
© f · CC0-1.0 · f/prompts.chat