dependency-sync

Detect new imports in modified files and install missing dependencies across package managers.

8|1|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/Consiliency/treesitter-chunker --skill dependency-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-sync
Source: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/dependency-sync
Command: npx skills add https://github.com/Consiliency/treesitter-chunker --skill dependency-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automatically detects new imports in modified source files and updates the appropriate package manifests to keep dependencies in sync, saving time and preventing drift.

Core Features & Use Cases

  • Automatic detection of new imports from modified files
  • Manifest-aware installation across npm/yarn, uv/poetry, pip, cargo, go mod, and other ecosystems
  • Optional docs-audit triggering and commit of manifest changes after installation
  • Use Case: After implementing a feature, run this skill to ensure package.json, pyproject.toml, and requirements.txt reflect new dependencies

Quick Start

After implementing code, run the dependency-sync workflow to update manifests across your project. Example: /ai-dev-kit:dependency-sync

Frequently Asked Questions about dependency-sync

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

FAQPage Schema
How do I automatically update package manifests when I add new imports?

Dependency-sync detects new imports in modified source files and automatically installs missing packages to the appropriate manifest—package.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod, or equivalent—keeping your dependencies synchronized with your code changes.

Does dependency-sync work with multiple package managers in the same project?

Yes, dependency-sync supports npm, yarn, uv, poetry, pip, cargo, go mod, and other ecosystems. It analyzes git diffs to identify which manifest corresponds to each modified file and installs dependencies in the correct package manager for that language.

When should I run dependency-sync in my workflow?

Run dependency-sync after implementing a feature that introduces new imports. It parses your code changes, installs missing packages, optionally triggers docs-audit, and can commit the updated manifests—automating the step that prevents dependency drift.

Can dependency-sync commit my manifest changes automatically?

Yes, dependency-sync can trigger docs-audit and commit manifest changes after installation, automating the full cycle from code change to version control so your repository stays current without manual steps.

What happens if dependency-sync can't identify a package for an import?

Dependency-sync analyzes git diffs and parses imports to match them to packages. If an import cannot be resolved to a known package, the installation step for that dependency is skipped; review unmatched imports manually to ensure accuracy.