Verifies the claude-dev-env installer lifecycle in a disposable sandboxed home directory.
npx skills add https://github.com/jl-cmd/claude-dev-env --skill verify-jl-cmd
Please help me install this Agent Skill. Skill: verify Source: https://github.com/jl-cmd/claude-dev-env/tree/main/.agents/skills/verify Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill verify-jl-cmd
--help, full install, and --uninstall with HOME, USERPROFILE, and GIT_CONFIG_GLOBAL redirected to a temporary sandbox, asserting 21 checks on the resulting tree. - Environment doctor: A read-only doctor command confirms Node 18+, Git, Python, the driver script, and the package directory are present before any verification run. - Feature maps and evidence: Per-feature verification guides under features/ cover hooks, Codex accounts, merge readiness, and privacy gates, with transcripts and doctor records stored as JSON evidence. - Use Case: After changing a hook registration in the installer, run the verify skill to confirm the sandboxed install produces the expected settings.json hook roster, skills pointer, and manifest without touching your real configuration. ## Quick Start Ask the AI to run the verify skill's installer check from the repository root using the verify-installer.mjs run command and report whether all checks passed.High-intent search queries and answers about installing and using this skill.
Run the installer with HOME, USERPROFILE, and GIT_CONFIG_GLOBAL pointed at a temporary sandbox directory. The verify skill's driver does this automatically, so install and uninstall writes land only in the throwaway tree.
Run node .agents/skills/verify/scripts/verify-installer.mjs run from the repository root. It asserts the manifest, settings.json hook roster, skills directory pointer, rules, and CLAUDE.md hub, reporting 21/21 checks passed on success.
The doctor command checks for Node.js 18 or later, Git on PATH, a working Python 3 interpreter, the driver script, and the package directory. Run node .agents/skills/verify/scripts/verify-installer.mjs doctor and continue only when it prints ready.
Git may flag the checkout as dubious ownership, blocking the installer's source-conflict guard. The driver seeds the sandbox GIT_CONFIG_GLOBAL with safe.directory = * so the guard runs while the real global Git config stays untouched.
No. Running bin/install.mjs directly writes to the live ~/.claude and ~/.agents directories and the global Git configuration. Always use the verify skill's driver, which isolates every side effect in a sandbox it removes afterward.
Grupo-6-ADS-BCreates isolated git worktrees with directory selection, ignore verification, and baseline test validation.
basicmachines-coResolves pull request feedback and failed checks, then re-runs the Codex review gate.
aprin-labsDocuments the Archimedes repo's conda environment, hermetic pytest conventions, merge-commit branch policy, and CI quality gates.
mirzadhamClassifies ECC components into DAILY and LIBRARY buckets using repo evidence.