Skip to content
Skills Library
DevOps & cloud · Planning

dependency-lifecycle

/dependency-lifecycle

Define a dependency lifecycle policy — patch/minor/major upgrade cadence, SBOM refresh, CVE triage, EOL tracking, automated PRs, lockfile hygiene, and supply-chain pinning. Use when: define our dependency upgrade cadence, set up a dependency lifecycle policy, triage these cve advisories, refresh the sbom for the next release, track end-of-life dependencies, configure automated dependency pull requests, enforce lockfile and pinning hygiene.

Repository
gabbe ↗
Licence
CC-BY-4.0
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

CC-BY-4.0, otwarta.

What it does and when to use it

Define a dependency lifecycle policy — patch/minor/major upgrade cadence, SBOM refresh, CVE triage, EOL tracking, automated PRs, lockfile hygiene, and supply-chain pinning. Use when: define our dependency upgrade cadence, set up a dependency lifecycle policy, triage these cve advisories, refresh the sbom for the next release, track end-of-life dependencies, configure automated dependency pull requests, enforce lockfile and pinning hygiene.

Original author description

Define a dependency lifecycle policy — patch/minor/major upgrade cadence, SBOM refresh, CVE triage, EOL tracking, automated PRs, lockfile hygiene, and supply-chain pinning. Use when: define our dependency upgrade cadence, set up a dependency lifecycle policy, triage these cve advisories, refresh the sbom for the next release, track end-of-life dependencies, configure automated dependency pull requests, enforce lockfile and pinning hygiene.

How it works

  1. Goal
  2. Steps
  3. Constraints
  4. Output Format
  5. Security & Guardrails
Original SKILL.md headings · 49 lines, 835 words
SKILL.md preview
---
name: dependency-lifecycle
description: "Define a dependency lifecycle policy — patch/minor/major upgrade cadence, SBOM refresh, CVE triage, EOL tracking, automated PRs, lockfile hygiene, and supply-chain pinning. Use when: define our dependency upgrade cadence, set up a dependency lifecycle policy, triage these cve advisories, refresh the sbom for the next release, track end-of-life dependencies, configure automated dependency pull requests, enforce lockfile and pinning hygiene."
license: CC-BY-SA-4.0
metadata:
  source: "agents/skills/ops/dependency-lifecycle.skill.md"
  tags: "ops, dependencies, supply-chain, maintenance"
  core: "false"
  context_cost: "medium"
---
# Dependency Lifecycle Skill

## Goal
Produce a dependency lifecycle policy that keeps a project's third-party dependencies current, supported, and free of known vulnerabilities without churn-driven breakage. It sets the cadence for absorbing patch, minor, and major updates, keeps the SBOM and CVE posture fresh, tracks end-of-life (EOL) before it bites, and enforces lockfile and pinning hygiene. This complements `dependency-security.skill` (which owns SBOM generation and SCA scanning mechanics) by defining the ongoing *operational rhythm* around it.

## Steps
1. **Inventory and classify.** Enumerate direct and transitive dependencies and classify each by blast radius (runtime-critical, build-only, dev-only) and update risk. Distinguish **patch** (bug/security, low risk — adopt fast), **minor** (backward-compatible features, moderate risk — batched), and **major** (breaking, high risk — planned with migration work).
2. **Set the cadence.** Define the rhythm per class: patch/security as soon as CI passes; minor on a regular batched window (e.g., weekly/biweekly); major as scheduled, owned migration tasks. State who reviews and merges each class.
3. **Refresh the SBOM.** Tie SBOM regeneration to the release pipeline so every shipped artifact has a current bill of materials. Diff the SBOM between releases to surface newly introduced or removed components. Defer generation mechanics to `dependency-security.skill`.
4. **Triage CVEs.** When an advisory lands, assess: is the vulnerable package actually used, is the vulnerable code path reachable, and what is the severity/exploitability in context. Prioritize remediation (upgrade, patch, or compensating control) by real risk, not raw CVSS alone. Record decisions in the audit trail.
5. **Track EOL.** Maintain a list of dependencies (and runtimes/base images) approaching end-of-support, with the EOL date and the planned migration target. EOL software stops receiving security fixes — schedule the move before the date, not after.
6. **Automate dependency PRs.** Configure automated update PRs (grouped by class to reduce noise), with CI gates that must pass before merge. Auto-merge is permissible only for patch/dev updates with green CI and human review reserved for minor/major.
7. **Enforce lockfile hygiene.** Require committed, deterministic lockfiles; every dependency change updates the lockfile in the same PR. Reject PRs that change manifests without the corresponding lockfile update. Verify resolved versions match the lockfile in CI.
8. **Pin the supply chain.** Pin dependencies (and CI actions/base images) to exact versions or integrity hashes/digests rather than floating ranges or mutable tags, so builds are reproducible and a hijacked upstream tag cannot silently change resolved code.
9. **Assign ownership and write the policy.** Name owners for each class and for EOL tracking, then assemble the Output Format below.

## Constraints
- Patch/security updates are adopted promptly; majors are always planned migration work, never auto-merged.
- The SBOM is regenerated for every release artifact, not occasionally.
- CVE triage prioritizes by reachability and exploitability in context, not CVSS score alone, and records the decision.
- Lockfiles are committed, deterministic, and updated atomically with manifest changes.
- Dependencies, CI actions, and base images are pinned to exact versions or digests; mutable tags are not acceptable for reproducible builds.
- This skill defines policy and proposes PRs; it does not auto-merge minor/major changes or override CI gates without human approval.

## Output Format
A dependency lifecycle policy in Markdown:
- **Inventory & classification** — dependency classes (runtime/build/dev) and update-risk tiers.
- **Cadence** — table of patch/minor/major rhythm, reviewer, merge rule.
- **SBOM** — regeneration trigger and diff process (cross-link `dependency-security.skill`).
- **CVE triage** — assessment criteria and prioritization rule.
- **EOL tracking** — table of dependency, EOL date, migration target, owner.
- **Automation** — PR grouping, CI gates, auto-merge boundaries.
- **Lockfile & pinning** — hygiene rules and pinning policy (versions/digests).
- **Owners** — named owners per class and for EOL.

## Security & Guardrails

### 1. Skill Security
- **Risk**: Adopting a malicious or typosquatted package during an "upgrade." Mitigation: verify package provenance/integrity hashes, restrict installs to approved registries, and review new transitive additions in dependency PRs.
- **Risk**: A CVE dismissed as "not exploitable" without evidence, leaving a real hole. Mitigation: require a documented reachability/exploitability justification recorded in the audit trail for any advisory marked as accepted-risk.

### 2. System Integration Security
- **Risk**: Floating version ranges or mutable CI action tags letting a hijacked upstream inject code into the build. Mitigation: pin to exact versions or commit/digest hashes and verify integrity in CI; treat un-pinning as a security-reviewed change.
- **Risk**: Auto-merge bots merging a poisoned or breaking update with weak CI. Mitigation: gate all auto-merge on the full CI suite plus SCA scan; restrict auto-merge to patch/dev classes with required status checks under branch protection.

### 3. LLM & Agent Guardrails
- **Risk**: The agent bumping a major version and "fixing" the breakage by deleting tests or loosening assertions. Mitigation: major upgrades are human-reviewed migration tasks; the agent may not weaken test coverage to make an upgrade pass.
- **Risk**: The agent suppressing or down-ranking a security advisory to keep a PR green. Mitigation: CVE severity may not be edited by the agent; unresolved advisories above the policy threshold block merge and escalate to a human.

Versions

The database has no other skills named dependency-lifecycle.

Database snapshot: 13.11.2026 · package version 574232546941 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100manage-dependencies
    Set and enforce dependency & package management across a monorepo: version policy (single-version vs independent), lockfile hygiene (commit + freeze in CI), automated batched upgrades (renovate/dependabot), supply-chain hygiene (SBOM, provenance/SLSA, digest pinning), and staged…
  • 100dependabot-review
    Reviews open Dependabot PRs, classifies by risk (patch/minor/major, security, lockfile-only), and merges safe ones or advises on what to do. Use when user mentions "dependabot", "dependabot PRs", "dependency updates", "merge dependabot", "review dependabot", "dependency PRs",…
  • 90dependency-auditor
    Audit the software supply chain - vulnerable and outdated dependencies, CVEs, lockfile integrity, license risks, typosquatting, and SBOM generation. Use for /lineage, dependency reviews, or "are our packages safe?" questions.
  • 95dependency-management
    Use this skill when the user says 'Dependabot', 'Renovate', 'dependencies', 'lock file', 'vulnerability scanning', 'update strategy', 'Renovate config', 'dependabot.yml', 'dependency bump', 'automated updates', 'version pinning', 'patch management', 'supply chain security', 'npm…
  • 98auditing-supply-chain
    Audit software supply chain risk — dependency and transitive package review, typosquatting and dependency confusion, lockfile and SBOM analysis, CI/CD pipeline and GitHub Actions security, build provenance, and secrets exposure. Use when assessing third-party package risk,…
  • 95ci-cd-supply-chain
    Use this capability for Git workflow, pull request policy, branch protection, CI/CD, build pipelines, release automation, dependency management, SBOM, provenance, SLSA, signing, container scanning, lockfiles, and supply-chain security. Trigger on CI, CD, pipeline, Git, branch,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.