sync-deps

Scan Python source files and notebooks to synchronize dependency manifests.

1|Updated Jun 25, 2025

Search Tags:#dependency management #python #dependencies #pyproject.toml #sync #requirements.txt

Ready to run

npx skills add https://github.com/laceto/rss_feed --skill sync-deps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-deps
Source: https://github.com/laceto/rss_feed/tree/main/.claude/skills/sync-deps
Command: npx skills add https://github.com/laceto/rss_feed --skill sync-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of synchronizing dependency files across a project, ensuring consistency between requirements.txt, pyproject.toml, and other dependency manifests based on actual code imports.

Core Features & Use Cases

Automated Dependency Management: Scans Python source files and notebooks to identify third-party imports.
Single Source of Truth: Derives dependencies from imports, eliminating manual bookkeeping and drift between dependency files.
Use Case: After adding new libraries to your project, use this Skill to automatically update requirements.txt and pyproject.toml to reflect these changes, ensuring your project's dependencies are always up-to-date and accurate.

Quick Start

Run the dependency synchronization script to update all dependency files.

Frequently Asked Questions about sync-deps

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

FAQPage Schema

How do I automatically sync Python dependencies across requirements.txt and pyproject.toml?▼

Syncing dependencies across requirements.txt and pyproject.toml is done by scanning source files and notebooks for third-party imports, resolving PyPI package names, and updating all manifests to reflect the installed versions.

What is the best way to prevent dependency drift in a Python project?▼

Preventing dependency drift in a Python project is achieved by deriving dependencies directly from actual code imports, creating a single source of truth that eliminates manual bookkeeping and ensures manifests stay aligned with your codebase.

Does dependency synchronization work with Jupyter notebooks and environment.yml files?▼

Dependency synchronization works with Jupyter notebooks and environment.yml files by scanning notebooks for third-party imports alongside Python source files, then updating environment.yml, setup.cfg, requirements.txt, and pyproject.toml with resolved versions.

How do I update requirements.txt after adding new imports to my Python code?▼

Updating requirements.txt after adding new imports is handled by running the synchronization script, which detects the new third-party imports in your source files, resolves their PyPI package names, and writes the installed versions to requirements.txt.

Can I use this to manage dependencies across multiple manifest formats simultaneously?▼

Managing dependencies across multiple manifest formats simultaneously is supported by updating requirements.txt, pyproject.toml, environment.yml, and setup.cfg in one pass, ensuring all files reflect the same resolved PyPI package versions from your code imports.

Why do my dependency files keep drifting from actual Python imports?▼

Dependency files drift from actual Python imports when manifests are maintained manually, a problem this Skill solves by automatically scanning source files and notebooks to derive dependencies directly from code, ensuring manifests match the real imports.