dependency-observation

Detect dependency misalignment between lockfiles and installed dependencies.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill dependency-observation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-observation
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/dependency-observation
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill dependency-observation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects dependency drift and reproducibility issues across environments.

Core Features & Use Cases

  • Lockfile verification and CI integration
  • Minimal integration smoke tests for dependencies
  • Dependency graph observation

Quick Start

Validate lockfile integrity and run a small smoke test to ensure dependencies are reproducible.

Frequently Asked Questions about dependency-observation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure dependencies are reproducible across environments?

Reproducible dependency installs require lockfile integrity verification. This Skill identifies misalignment between declared lockfiles and installed dependencies, validating fixed versions across Node.js, Python, Go, Rust, and Ruby to prevent non-reproducible builds in local, CI, and deployment environments.

What causes dependency drift between my lockfile and installed packages?

Dependency drift occurs when lockfile specifications diverge from actual installed versions, often during environment setup or cross-platform deployments. This Skill detects that misalignment by observing dependency graphs and enforcing lockfile integrity through cache-free clean builds.

Can I validate lockfile integrity in CI pipelines?

Yes. This Skill integrates lockfile verification into CI workflows, running minimal integration smoke tests and cache-free builds to validate fixed versions before deployment. It logs startup dependency versions and outputs dependency graphs for visibility.

How do I detect when a dependency update breaks reproducibility?

Dependency observation detects breaks by performing cache-free clean builds and running minimal integration smoke tests after updates. The Skill identifies version misalignments and logs dependency changes, surfacing reproducibility issues before they reach production.

Does this work with monorepos or multiple lock files?

This Skill observes dependency graph changes across Node.js, Python, Go, Rust, and Ruby, applicable during dependency addition, updates, and cross-environment deployments. It validates fixed versions regardless of project structure or lockfile configuration.

What's the difference between lockfile verification and smoke testing?

Lockfile verification enforces that declared versions match installed packages; smoke testing validates that dependencies actually function together. This Skill combines both, verifying integrity and running minimal integration tests to ensure full reproducibility.