switch-env

Sterne12

Forks1

Aktualisiert12. März 2026 um 19:42

Switch trickle packages between local symlinked development versions and published registry versions. Use when the user asks to switch to local/dev/symlinked, switch to published/production/registry, or test with published packages.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

yiheinchai

yiheinchai/trickle

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	switch-env
description	Switch trickle packages between local symlinked development versions and published registry versions. Use when the user asks to switch to local/dev/symlinked, switch to published/production/registry, or test with published packages.
disable-model-invocation	true
argument-hint	[local\|published]

Switch Trickle Package Environment

Switches all trickle packages between local development (symlinked) and published (registry) versions.

Switch to local (symlinked)

For development — uses the source code directly so changes are reflected immediately.

# npm: link CLI and JS client globally
cd packages/cli && npm link
cd packages/client-js && npm link

# Python: editable install
cd packages/client-python && pip install -e .

# VSCode extension: copy built dist to installed extension
cd packages/vscode-extension && npm run build
cp dist/extension.js ~/.vscode/extensions/yiheinchai.trickle-vscode-*/dist/extension.js

Then tell the user to reload VSCode.

Switch to published (registry)

For testing what end users will get from npm/PyPI.

# npm: unlink and install from registry
npm unlink -g trickle-cli
npm unlink -g trickle-observe
npm install -g trickle-cli
npm install -g trickle-observe

# Python: uninstall editable, install from PyPI
pip uninstall trickle trickle-observe -y
pip install trickle-observe

Verify

After switching, verify with:

# Check CLI — symlink vs real install
which trickle && ls -la $(which trickle)

# Check Python — look for "Editable project location" (local) vs plain Location (published)
pip show trickle-observe | grep -E "Version|Location|Editable"

# Check npm global
npm ls -g trickle-observe trickle-cli --depth=0

Important notes

The old Python package name was trickle (editable install). If switching from local to published, uninstall both trickle AND trickle-observe to avoid conflicts.
Python uses /opt/anaconda3/bin/python — system python3 points to 3.14 which may lack build tools.
After switching VSCode extension, user must reload VSCode (Cmd+Shift+P -> "Developer: Reload Window").

Mehr aus diesem Repository

gleiches Repository

create-skill

yiheinchai/trickle

Create a new Claude Code skill. Use when the user wants to create, scaffold, build, or set up a new skill, custom slash command, or reusable instruction for Claude Code. Also use when someone says "make a skill", "I keep repeating myself to Claude", or "teach Claude how to do X".

2026-03-1712

publish

yiheinchai/trickle

Publish all trickle packages (npm, PyPI, VSCode extension). Use when the user asks to publish, release, bump versions, or push packages to registries.

2026-03-1712

dogfood-trickle

yiheinchai/trickle

Dogfood trickle by creating real demo projects, running trickle on them, finding bugs and UX issues, then fixing and publishing them. Use when asked to test trickle, dogfood, find bugs, try trickle on a real project, or improve trickle's developer experience. Also use when someone says "test trickle on react", "try trickle with python", "dogfood ML workflow", etc.

2026-03-1512

Switch Trickle Package Environment

Switches all trickle packages between local development (symlinked) and published (registry) versions.

Switch to local (symlinked)

For development — uses the source code directly so changes are reflected immediately.

# npm: link CLI and JS client globally cd packages/cli && npm link cd packages/client-js && npm link # Python: editable install cd packages/client-python && pip install -e . # VSCode extension: copy built dist to installed extension cd packages/vscode-extension && npm run build cp dist/extension.js ~/.vscode/extensions/yiheinchai.trickle-vscode-*/dist/extension.js

Then tell the user to reload VSCode.

Switch to published (registry)

For testing what end users will get from npm/PyPI.

# npm: unlink and install from registry npm unlink -g trickle-cli npm unlink -g trickle-observe npm install -g trickle-cli npm install -g trickle-observe # Python: uninstall editable, install from PyPI pip uninstall trickle trickle-observe -y pip install trickle-observe

Verify

After switching, verify with:

# Check CLI — symlink vs real install which trickle && ls -la $(which trickle) # Check Python — look for "Editable project location" (local) vs plain Location (published) pip show trickle-observe | grep -E "Version|Location|Editable" # Check npm global npm ls -g trickle-observe trickle-cli --depth=0

Important notes

The old Python package name was trickle (editable install). If switching from local to published, uninstall both trickle AND trickle-observe to avoid conflicts.

Python uses /opt/anaconda3/bin/python — system python3 points to 3.14 which may lack build tools.

After switching VSCode extension, user must reload VSCode (Cmd+Shift+P -> "Developer: Reload Window").