verify
Verifies the claude-dev-env command-line installer in a disposable home. Maps checks for configuration projections, hooks, policy lint, and continuous integration.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- verify
- description
- Verifies the claude-dev-env command-line installer in a disposable home. Maps checks for configuration projections, hooks, policy lint, and continuous integration.
02 资源文件 20
- 参考文档features/claude-configuration-surfaces.md664 B
- 参考文档features/codex-accounts.md7.2 KB
- 参考文档features/codex-sol-prompt.md2.6 KB
- 参考文档features/cross-tool-projection.md736 B
- 参考文档features/follow-up-ledger.md4.9 KB
- 参考文档features/hook-lifecycle.md6.2 KB
- 参考文档features/installer-lifecycle.md3.0 KB
- 参考文档features/merge-readiness.md5.4 KB
- 参考文档features/posting-and-privacy-gates.md6.9 KB
- 参考文档features/pr-visual.md1.7 KB
- 参考文档features/README.md690 B
- 参考文档features/release-publish.md7.0 KB
- 参考文档features/scoped-installation.md624 B
- 参考文档features/second-claude-account.md3.4 KB
- 脚本scripts/driver.mjs13.2 KB
- 脚本scripts/driver.test.mjs3.0 KB
- 脚本scripts/verify_installer_constants/constants.mjs1.4 KB
- 脚本scripts/verify_installer_constants/constants.test.mjs599 B
- 脚本scripts/verify-installer.mjs9.2 KB
- 脚本scripts/verify-installer.test.mjs4.7 KB
03 SKILL.md 正文
Verify claude-dev-env
Run the installer with disposable home and Git configuration roots. Never use the live install commands for verification.
This skill and its feature maps live in .agents/skills/verify/, which Codex reads. .claude/skills and .cursor/skills are directory pointers to .agents/skills, so Claude Code and Cursor read the same files. Add a new feature map here and link it from features/README.md. tests/test_repository_skill_pointers.py fails when a pointer turns into a directory or a map is missing from the index.
Launch
Run this command from the repository root:
node .agents/skills/verify/scripts/verify-installer.mjs run
The command succeeds when the transcript reports 23/23 checks passed and ALL CHECKS PASSED. The driver removes its sandbox before the helper exits.
Doctor
Run the read-only environment check first:
node .agents/skills/verify/scripts/verify-installer.mjs doctor
Continue only when the command prints Doctor command: ready.
Drive
run covers the installer lifecycle only. It calls .agents/skills/verify/scripts/driver.mjs.
For other changes, use the matching file in features. Exercise each changed feature before you verify.
Policy linter
Run cde lint through Node.js:
node packages/claude-dev-env/bin/cde.mjs lint --files <path>
node packages/claude-dev-env/bin/cde.mjs lint --staged
node packages/claude-dev-env/bin/cde.mjs lint --base origin/main
node packages/claude-dev-env/bin/cde.mjs lint --repository
Get-Content -Raw .\src\file.py | node packages/claude-dev-env/bin/cde.mjs lint --text-as .\src\file.py
Use --format text, --format json, or --format editor. Relative --files and --text-as paths resolve from the caller directory, including a caller directory below the repository root. Use --python <command> to pick the Python interpreter.
Exit 0 is clean. Exit 1 reports diagnostics. Exit 2 reports invalid input or a launcher start failure. Exit 3 reports an incomplete rule run.
Do not run node packages/claude-dev-env/bin/install.mjs without an isolated home. That command writes to the user configuration directories.
Evidence
Store evidence in tests/audit/data/hook-linter-conversion/evidence/.
installer-doctor.jsonrecords tool availability.installer-transcript.jsonrecords the command, exit status, actions, and results.
The transcript must show each installer step and its result. Inspect installed settings, Codex hooks, Git configuration, and manifests when a change affects them.
Cleanup
The installer driver removes only the temporary directory that it creates. It does not kill processes by name.
After each run, confirm that the transcript contains Sandbox removed. Keep the evidence files.
Helpers
Run these helpers:
node .agents/skills/verify/scripts/verify-installer.mjs doctor
node .agents/skills/verify/scripts/verify-installer.mjs run
node --test .agents/skills/verify/scripts/verify-installer.test.mjs
python -m pytest packages/claude-dev-env/scripts/tests/test_policy_lint_selection.py packages/claude-dev-env/scripts/tests/test_policy_lint_rules_engine.py packages/claude-dev-env/scripts/tests/test_policy_lint_rules_registry.py packages/claude-dev-env/scripts/tests/test_cde_lint.py -q
node --test packages/claude-dev-env/bin/cde.test.mjs
04 同仓库更多 Skills
update
Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.
source-command-sr-loop
Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean
skill-builder
Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.
session-tidy
Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.
session-log
Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.
run-claude-dev-env
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.