メニュー
Package managers: uv (Python), bun (TypeScript). Use when setting up uv or bun, migrating from pip/npm/yarn/poetry/pipenv, or resolving lockfile conflicts.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-package-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-06-01T00:00:00.000Z" |
| reviewed | "2026-06-01T00:00:00.000Z" |
| description | Package managers: uv (Python), bun (TypeScript). Use when setting up uv or bun, migrating from pip/npm/yarn/poetry/pipenv, or resolving lockfile conflicts. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--manager <uv|bun|npm|cargo>] |
| argument-hint | [--check-only] [--fix] [--manager <uv|bun|npm|cargo>] |
| name | configure-package-management |
Check and configure modern package managers for optimal development experience.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up a new project with modern package managers (uv, bun) | Installing a single dependency — run uv add or bun add directly |
| Migrating from legacy package managers (pip, npm, yarn, poetry) to modern ones | Project uses cargo or go mod (already optimal, no migration needed) |
| Auditing package manager configuration for best practices | Configuring linting or formatting tools — use /configure:linting |
| Ensuring lock files, dependency groups, and CI/CD integration are properly configured | Resolving a specific dependency conflict — debug with uv pip compile or bun install --verbose |
| Detecting and cleaning up conflicting lock files from multiple managers | Only need to install dependencies — run uv sync or bun install directly |
pwdfind . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)find . -maxdepth 1 \( -name 'uv.lock' -o -name 'bun.lockb' -o -name 'package-lock.json' -o -name 'yarn.lock' -o -name 'pnpm-lock.yaml' -o -name 'poetry.lock' -o -name 'Pipfile.lock' \)find . -maxdepth 1 -type d -name '.venv'find . -maxdepth 1 \( -name 'requirements.txt' -o -name 'Pipfile' \)find . -maxdepth 1 -name '.project-standards.yaml'Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--manager <uv|bun|npm|cargo>: Override detection (focus on specific manager)Modern package manager preferences:
Execute this package management compliance check:
Check for language and manager indicators:
| Indicator | Language | Current Manager | Recommended |
|---|---|---|---|
pyproject.toml | Python | uv / poetry / pip | uv |
requirements.txt | Python | pip | uv |
Pipfile | Python | pipenv | uv |
poetry.lock | Python | poetry | uv |
uv.lock | Python | uv | uv |
package.json + bun.lockb | JavaScript/TypeScript | bun | bun |
package.json + package-lock.json | JavaScript/TypeScript | npm | bun |
package.json + yarn.lock | JavaScript/TypeScript | yarn | bun |
package.json + pnpm-lock.yaml | JavaScript/TypeScript | pnpm | bun |
Cargo.toml | Rust | cargo | cargo |
go.mod | Go | go mod | go mod |
Use WebSearch or WebFetch to verify latest versions before configuring.
For each detected language, check configuration:
Python (uv):
uv installed and on PATHpyproject.toml exists with [project] sectionuv.lock exists (lock file).venv/pyproject.tomlhatchling, setuptools, etc.)JavaScript/TypeScript (bun):
bun installed and on PATHpackage.json existsbun.lockb exists (lock file)node_modules/ existsdev, build, test, lint)Print a formatted compliance report:
Package Management Configuration Report
=======================================
Project: [name]
Languages: Python, TypeScript
Python:
Package manager uv 0.5.x [MODERN | LEGACY pip]
pyproject.toml exists [EXISTS | MISSING]
Lock file uv.lock [EXISTS | OUTDATED | MISSING]
Virtual environment .venv/ [EXISTS | MISSING]
Python version 3.12 [PINNED | NOT PINNED]
Dependency groups dev, test, docs [CONFIGURED | MINIMAL]
Build backend hatchling [CONFIGURED | MISSING]
JavaScript/TypeScript:
Package manager bun 1.1.x [MODERN | npm | yarn]
package.json exists [EXISTS | MISSING]
Lock file bun.lockb [EXISTS | MISSING]
Scripts dev, build, test, lint [COMPLETE | INCOMPLETE]
Type definitions tsconfig.json [CONFIGURED | MISSING]
Engine constraints package.json engines [PINNED | NOT PINNED]
Overall: [X issues found]
Recommendations:
- Migrate from pip to uv for faster installs
- Add uv.lock to version control
- Configure dependency groups in pyproject.toml
- Migrate from npm to bun for better performance
If --check-only, stop here.
Apply configuration based on detected languages. Use templates from REFERENCE.md:
uv init or migrate from existing managerpyproject.toml with project metadata and dependency groupsuv.lock.gitignorepackage-lock.json, yarn.lock, pnpm-lock.yaml)bun install to generate bun.lockbpackage.json.gitignoreIf migrating from a legacy manager:
pip/poetry to uv:
uv inituv add -r requirements.txt or copy from poetryrequirements.txt, Pipfile, poetry.lock)npm/yarn/pnpm to bun:
node_modulesbun installUse migration templates from REFERENCE.md.
Update GitHub Actions workflows to use modern package managers:
pip install with astral-sh/setup-uv@v8 + uv syncactions/setup-node with oven-sh/setup-bun@v2Use CI workflow templates from REFERENCE.md.
Update .project-standards.yaml:
standards_version: "2025.1"
last_configured: "[timestamp]"
components:
package_management: "2025.1"
python_package_manager: "uv"
javascript_package_manager: "bun"
lock_files_committed: true
Print a summary of changes applied, migrations performed, and next steps for verifying the configuration.
For detailed configuration templates and migration guides, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:package-management --check-only |
| Auto-fix all issues | /configure:package-management --fix |
| Check uv version | uv --version |
| Check bun version | bun --version |
| List Python deps | uv pip list --format json |
| List JS deps | bun pm ls --json |
| Flag | Description |
|---|---|
--check-only | Report status without offering migrations |
--fix | Apply all migrations automatically without prompting |
--manager <manager> | Override detection (uv, bun, npm, cargo) |
# Check compliance and offer migrations
/configure:package-management
# Check only, no modifications
/configure:package-management --check-only
# Auto-migrate Python to uv
/configure:package-management --fix --manager uv
# Auto-migrate JavaScript to bun
/configure:package-management --fix --manager bun
/configure:linting - Configure linting tools (ruff, biome)/configure:formatting - Configure formatters/deps:install - Universal dependency installer/configure:all - Run all compliance checksInstall, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.