sync-deps — for Claude Code sync-deps, financialtools, community, for Claude Code, ide skills, requirements.txt, pyproject.toml, The script outputs one, IMPORT_TO_PACKAGE, pytest

v1.0.0

이 스킬 정보

적합한 상황: Ideal for AI agents that need derives the project's dependency list from actual imports in source files — one. 현지화된 요약: # Sync Dependencies Derives the project's dependency list from actual imports in source files — one scan, one canonical list, propagated to every dep file. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

기능

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"

# 핵심 주제

laceto laceto
[1]
[0]
업데이트: 3/21/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

적합한 상황: Ideal for AI agents that need derives the project's dependency list from actual imports in source files — one. 현지화된 요약: # Sync Dependencies Derives the project's dependency list from actual imports in source files — one scan, one canonical list, propagated to every dep file. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

이 스킬을 사용하는 이유

추천 설명: sync-deps helps agents derives the project's dependency list from actual imports in source files — one. Sync Dependencies Derives the project's dependency list from actual imports in source files — one scan, one

최적의 용도

적합한 상황: Ideal for AI agents that need derives the project's dependency list from actual imports in source files — one.

실행 가능한 사용 사례 for sync-deps

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

! 보안 및 제한 사항

  • 제한 사항: update IMPORT TO PACKAGE in the script — that is the only place to change.
  • 제한 사항: Runtime dependencies — generated by sync-deps, do not edit by hand.
  • 제한 사항: Preserve all other sections unchanged (surgical edit only).

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Labs 데모

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 및 설치 단계

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

? 자주 묻는 질문

sync-deps은 무엇인가요?

적합한 상황: Ideal for AI agents that need derives the project's dependency list from actual imports in source files — one. 현지화된 요약: # Sync Dependencies Derives the project's dependency list from actual imports in source files — one scan, one canonical list, propagated to every dep file. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

sync-deps은 어떻게 설치하나요?

다음 명령을 실행하세요: npx killer-skills add laceto/financialtools/sync-deps. Cursor, Windsurf, VS Code, Claude Code와 19개 이상의 다른 IDE에서 동작합니다.

sync-deps은 어디에 쓰이나요?

주요 활용 사례는 다음과 같습니다: 사용 사례: Applying Derives the project's dependency list from actual imports in source files — one, 사용 사례: Applying scan, one canonical list, propagated to every dep file. No manual bookkeeping;, 사용 사례: Applying no drift between requirements.txt and pyproject.toml.

sync-deps 와 호환되는 IDE는 무엇인가요?

이 스킬은 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 와 호환됩니다. 통합 설치에는 Killer-Skills CLI를 사용하세요.

sync-deps에 제한 사항이 있나요?

제한 사항: update IMPORT TO PACKAGE in the script — that is the only place to change.. 제한 사항: Runtime dependencies — generated by sync-deps, do not edit by hand.. 제한 사항: Preserve all other sections unchanged (surgical edit only)..

이 스킬 설치 방법

  1. 1. 터미널 열기

    프로젝트 디렉터리에서 터미널 또는 명령줄을 여세요.

  2. 2. 설치 명령 실행

    npx killer-skills add laceto/financialtools/sync-deps 를 실행하세요. CLI가 IDE 또는 에이전트를 자동으로 감지하고 스킬을 설정합니다.

  3. 3. 스킬 사용 시작

    스킬이 이제 활성화되었습니다. 현재 프로젝트에서 sync-deps을 바로 사용할 수 있습니다.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

sync-deps

Install sync-deps, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

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

관련 스킬

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

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

현지화된 요약: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

333.8k
0
인공지능

widget-generator

Logo of f
f

현지화된 요약: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf

149.6k
0
인공지능

flags

Logo of vercel
vercel

현지화된 요약: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

현지화된 요약: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
개발자