document-dependency

Document software dependencies by identifying API divergences between AI training data and library implementations.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/kang-sw/devenv --skill document-dependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-dependency
Source: https://github.com/kang-sw/devenv/tree/main/claude-skills/document-dependency
Command: npx skills add https://github.com/kang-sw/devenv --skill document-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and updating of documentation that highlights discrepancies between a dependency's actual API and the knowledge embedded in AI models, ensuring accurate and up-to-date technical documentation.

Core Features & Use Cases

  • Dependency Documentation: Creates or updates delta documents for specific library versions.
  • API Divergence Tracking: Records where AI training data differs from the live API.
  • Automated Context Gathering: Scans project manifests and source code for relevant information.
  • Verification: Compares generated documentation against source code for accuracy.
  • Use Case: When a critical library like serde in a Rust project is updated, this skill can quickly generate a delta document showing what changed in the API and how the project uses those changes, ensuring the AI's understanding remains current.

Quick Start

Use the document-dependency skill to create or update the documentation for the 'tokio' dependency.

Frequently Asked Questions about document-dependency

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

FAQPage Schema
How do I document API divergence between AI training data and actual library implementations?

To document API divergence, this skill orchestrates the scanning of project source code and manifests to identify discrepancies between live library APIs and AI training data. It then delegates document creation and verification to specialized agents.

What is the best way to track dependency API changes after a library version update?

Tracking dependency API changes is handled by scanning project usage and source code locations to generate delta documents. This records where the AI's embedded knowledge differs from the actual updated library implementation.

How does automated context gathering work for dependency management?

Automated context gathering for dependency management works by scanning project manifests and source code to collect relevant information. This data is used to identify API divergences and generate accurate technical documentation.

Can I use this to generate API documentation for specific library versions in my code?

Yes, you can generate API documentation for specific library versions. The skill creates or updates delta documents by verifying the generated output against the actual source code to ensure technical accuracy.

Why should I track discrepancies between AI training data and live APIs?

Tracking discrepancies between AI training data and live APIs ensures your technical documentation remains accurate and up-to-date. It highlights where AI models have outdated knowledge about actual library implementations.

Does this skill work with Rust project dependencies like serde and tokio?

Yes, it works with dependencies like serde and tokio. The skill scans project usage of these libraries and generates delta documents showing what changed in the API and how the project uses those changes.