sync-deps — community sync-deps, rss_feed, community, ide skills

v1.0.0

Über diesen Skill

Perfekt für Python-Entwicklungsagenten, die eine automatisierte Abhängigkeitsverwaltung und -synchronisation benötigen. Synchronises all dependency files from the actual imports in the codebase. Use when asked to update requirements.txt, sync dependencies, update pyproject.toml dependencies, fix requirements, update deps, sync deps, update dependency files, or update renv/environment.yml. Scans all Python source files for third-party imports, resolves PyPI package names, fetches installed versions, then writes requirements.txt and updates pyproject.toml [project.dependencies] — keeping every dep file in sync with a single source of truth.

laceto laceto
[1]
[0]
Updated: 3/11/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Perfekt für Python-Entwicklungsagenten, die eine automatisierte Abhängigkeitsverwaltung und -synchronisation benötigen. Synchronises all dependency files from the actual imports in the codebase. Use when asked to update requirements.txt, sync dependencies, update pyproject.toml dependencies, fix requirements, update deps, sync deps, update dependency files, or update renv/environment.yml. Scans all Python source files for third-party imports, resolves PyPI package names, fetches installed versions, then writes requirements.txt and updates pyproject.toml [project.dependencies] — keeping every dep file in sync with a single source of truth.

Warum diese Fähigkeit verwenden

Ermächtigt die Agenten, die Abhängigkeitsliste eines Projekts aus den tatsächlichen Importen in den Quelldateien abzuleiten, wodurch die manuelle Buchhaltung und der Abstand zwischen requirements.txt und pyproject.toml eliminiert werden, unter Verwendung von Protokollen wie der Abhängigkeitsanalyse und Dateiformaten wie requirements.txt und pyproject.toml.

Am besten geeignet für

Perfekt für Python-Entwicklungsagenten, die eine automatisierte Abhängigkeitsverwaltung und -synchronisation benötigen.

Handlungsfähige Anwendungsfälle for sync-deps

Automatisieren von Abhängigkeitsaktualisierungen nach dem Hinzufügen oder Entfernen von Paketen
Abhängigkeitsdrift zwischen requirements.txt und pyproject.toml debuggen
Synchronisieren der Abhängigkeitsdateien vor einer Veröffentlichung

! Sicherheit & Einschränkungen

  • Benötigt Zugriff auf Quelldateien und Abhängigkeitsdateien
  • Nur Python-Projekte
  • Muss die tatsächlichen Importe in den Quelldateien scannen

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is sync-deps?

Perfekt für Python-Entwicklungsagenten, die eine automatisierte Abhängigkeitsverwaltung und -synchronisation benötigen. Synchronises all dependency files from the actual imports in the codebase. Use when asked to update requirements.txt, sync dependencies, update pyproject.toml dependencies, fix requirements, update deps, sync deps, update dependency files, or update renv/environment.yml. Scans all Python source files for third-party imports, resolves PyPI package names, fetches installed versions, then writes requirements.txt and updates pyproject.toml [project.dependencies] — keeping every dep file in sync with a single source of truth.

How do I install sync-deps?

Run the command: npx killer-skills add laceto/rss_feed/sync-deps. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for sync-deps?

Key use cases include: Automatisieren von Abhängigkeitsaktualisierungen nach dem Hinzufügen oder Entfernen von Paketen, Abhängigkeitsdrift zwischen requirements.txt und pyproject.toml debuggen, Synchronisieren der Abhängigkeitsdateien vor einer Veröffentlichung.

Which IDEs are compatible with sync-deps?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for sync-deps?

Benötigt Zugriff auf Quelldateien und Abhängigkeitsdateien. Nur Python-Projekte. Muss die tatsächlichen Importe in den Quelldateien scannen.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add laceto/rss_feed/sync-deps. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use sync-deps immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

sync-deps

Install sync-deps, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Sync Dependencies

Derives the project's dependency list from actual imports in source files — one scan, one canonical list, propagated to every dep file. No manual bookkeeping; no drift between requirements.txt and pyproject.toml.

When to Use This Skill

  • User says "update requirements.txt", "sync deps", "fix requirements", "update deps"
  • User says "update pyproject.toml dependencies", "sync dependency files"
  • After adding or removing a package to the project
  • Before a release or a code review

Single Source of Truth

source files (.py, .ipynb)
        │
        ▼
  sync_deps.py   ← ONE scan, ONE canonical list
        │
        ├──▶ requirements.txt
        ├──▶ pyproject.toml  [project.dependencies]
        ├──▶ environment.yml  (if present)
        └──▶ setup.cfg        (if present)

Everything is derived; never edit dep files by hand.


Step 1 — Run the scanner

Run the bundled script from the repo root (not from inside the skill folder):

bash
1python .claude/skills/sync-deps/scripts/sync_deps.py

The script outputs one package>=X.Y line per third-party dependency, sorted alphabetically, to stdout. Capture it:

bash
1python .claude/skills/sync-deps/scripts/sync_deps.py > /tmp/deps_raw.txt

Inspect the output before writing anything. If a package is missing or wrong, update IMPORT_TO_PACKAGE in the script — that is the only place to change.


Step 2 — Write requirements.txt

Replace the full content of requirements.txt at the repo root with:

# Runtime dependencies — generated by sync-deps, do not edit by hand.
# Regenerate with: python .claude/skills/sync-deps/scripts/sync_deps.py
#
<one line per package from stdout, sorted>

Rules:

  • Keep the header comment exactly as shown.
  • Packages are sorted case-insensitively.
  • Dev-only packages (pytest, mypy, ruff, pytest-cov) must not appear here — they belong in pyproject.toml [project.optional-dependencies].dev only.

Step 3 — Update pyproject.toml [project.dependencies]

Read pyproject.toml. Replace the dependencies = [...] list under [project] with the same package list from Step 1, formatted as TOML strings:

toml
1dependencies = [ 2 "package-a>=X.Y", 3 "package-b>=X.Y", 4]

Rules:

  • Preserve all other sections unchanged (surgical edit only).
  • Dev packages stay in [project.optional-dependencies].dev — do not move them.
  • If [project.optional-dependencies].dev is missing, add it with at minimum: ["pytest>=8", "pytest-cov", "mypy", "ruff"].

Step 4 — Update optional dep files (if present)

Scan the repo root for these files and update them if found:

environment.yml (conda)

Update the dependencies: list. Preserve - pip: sub-list structure. Example shape:

yaml
1dependencies: 2 - python>=3.9 3 - pip: 4 - package-a>=X.Y 5 - package-b>=X.Y

setup.cfg

If install_requires exists under [options], replace it with the new list:

ini
1[options] 2install_requires = 3 package-a>=X.Y 4 package-b>=X.Y

Pipfile

If present, update the [packages] section. Do not modify [dev-packages].


Step 5 — Verify and report

After all edits, print a summary:

sync-deps complete
─────────────────────────────────────────
Source files scanned : <N> .py files, <M> .ipynb files
Third-party imports  : <K>
─────────────────────────────────────────
Updated:
  requirements.txt          — <N> packages
  pyproject.toml            — [project.dependencies] (<N> entries)
  environment.yml           — (skipped — not found)
  setup.cfg                 — (skipped — not found)
─────────────────────────────────────────
Packages:
  <sorted package list, one per line>

Import-to-Package Name Map

The script maintains IMPORT_TO_PACKAGE — a dict mapping Python import names to their canonical PyPI package names. This is the only place to fix name mismatches. Never hardcode a mapping elsewhere.

Import namePyPI package
sklearnscikit-learn
PILPillow
cv2opencv-python
yamlPyYAML
bs4beautifulsoup4
dotenvpython-dotenv
faissfaiss-cpu
rank_bm25rank-bm25
langchain_classiclangchain-classic
langchain_corelangchain-core
langchain_communitylangchain-community
langchain_openailangchain-openai

To add a new mapping: edit IMPORT_TO_PACKAGE in scripts/sync_deps.py.


Exclusion Rules

These are never added to requirements.txt:

  • Standard library modules (os, sys, json, …)
  • The project's own package (auto-detected from pyproject.toml [project].name)
  • Dev-only packages: pytest, pytest-cov, mypy, ruff, black, isort
  • Private names (starting with _)
  • Modules in excluded directories: venv/, .venv/, build/, dist/, .eggs/

Troubleshooting

ProblemCauseFix
Package missing from outputImport name not in IMPORT_TO_PACKAGE and not installedAdd mapping to IMPORT_TO_PACKAGE or install the package
Wrong version shownPackage not installed in active venvActivate the correct venv before running
sys.stdlib_module_names not availablePython < 3.10Script falls back to a static stdlib set; update Python if possible
Package appears but shouldn'tImport from a test fixture or example that shadows a real nameAdd it to DEV_ONLY_PACKAGES in the script
pyproject.toml parse errorNon-standard TOML formattingRead the file carefully and apply a surgical edit

Verwandte Fähigkeiten

Looking for an alternative to sync-deps or another community skill for your workflow? Explore these related open-source skills.

Alle anzeigen

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
Künstliche Intelligenz

widget-generator

Logo of f
f

Erzeugen Sie anpassbare Widget-Plugins für das Prompts.Chat-Feed-System

149.6k
0
Künstliche Intelligenz

flags

Logo of vercel
vercel

Das React-Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensor und dynamische neuronale Netze in Python mit starker GPU-Beschleunigung

98.6k
0
Entwickler