run-claude-dev-env

Build, install, and smoke-test the claude-dev-env installer against a sandbox home directory.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill run-claude-dev-env-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-claude-dev-env
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/skill-archive/run-claude-dev-env
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill run-claude-dev-env-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the claude-dev-env installer directly writes into your real ~/.claude/ and ~/.agents/ directories and mutates global git config, making it risky to test or verify. This Skill provides a sandboxed smoke driver and clear run/test instructions so the installer can be exercised without touching real configuration. ## Core Features & Use Cases - Sandboxed Smoke Testing: The driver.mjs harness redirects HOME, USERPROFILE, and GIT_CONFIG_GLOBAL to a throwaway directory, then runs the --help, install, and --uninstall lifecycle with 21 assertions. - Real Install Guidance: Documents the human install path (node bin/install.mjs with --only, --update, --uninstall flags) and its side effects. - Troubleshooting Reference: Covers Python detection failures, git dubious-ownership errors, malformed settings.json, and Windows network-share npm issues. - Use Case: After modifying bin/install.mjs, run the driver to confirm a full install lands skills, agents, hooks, rules, and a manifest correctly, and that --uninstall removes every tracked file. ## Quick Start Run the claude-dev-env smoke driver to verify the installer works end to end against a sandbox home directory.

Frequently Asked Questions about run-claude-dev-env

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

FAQPage Schema
How do I test the claude-dev-env installer safely?▼

Run node .claude/skills/run-claude-dev-env/driver.mjs from the packages/claude-dev-env directory. The driver spawns the installer against a temporary sandbox home, runs the help, install, and uninstall lifecycle, and asserts 21 checks before deleting the sandbox.

How do I install claude-dev-env for real on my machine?▼

Run node bin/install.mjs to install every group, or node bin/install.mjs --only core for a selective install. This writes into your real ~/.claude/ and ~/.agents/ directories and sets a global git hooks path, so only run it when you mean to install.

What prerequisites does the claude-dev-env installer need?▼

The installer requires Node.js 18+, Python 3.8+, and git on PATH. On Windows it skips the Microsoft Store Python stub, so install Python from python.org if detection fails.

Why does the install fail with a git dubious ownership error?▼

The installer's source-conflict guard runs git status, which exits 128 on checkouts git distrusts, such as UNC network shares owned by another account. Add the exception with git config --global --add safe.directory '<repo-path>' and rerun.

Can the installer target a directory other than ~/.claude?▼

The install target is hardcoded to os.homedir()/.claude with no override flag. To redirect it, set HOME on POSIX and USERPROFILE on Windows to a temp directory, which is exactly what the smoke driver does automatically.

Why does npm install fail on a Windows network-share checkout?▼

npm symlinks the workspace package into root node_modules and the network share rejects the symlink with errno -4094. The package's own node_modules already carries its dependency, so the driver and tests still run without it.