القائمة
Use for cuenv tools runtime, tool sources, platform overrides, extraction behavior, activation, lock sync, and VCS dependencies. Covers schema/tools.cue and schema/vcs.cue.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for cuenv codegen, generated file language schemas, formatting, ignore files, CODEOWNERS, editorconfig, .rules.cue, and sync-provider drift. Covers schema/codegen.cue, schema/codegen/codegen.cue, schema/formatters.cue, schema/ignores.cue, schema/owners.cue, and schema/rules/*.
Use for cuenv task definitions, task groups, sequences, dependencies, params, inputs, outputs, captures, output refs, cache policy, hermetic execution, and task execution limitations. Covers schema/tasks.cue and schema/execution.cue.
Use when cutting a cuenv release manually: bumping the workspace Cargo version and internal crate dependency versions, refreshing Cargo.lock, creating annotated bare-version tags, creating GitHub releases, and monitoring the release workflow.
Use for cuenv CI schema, contributors, provider config, workflow sync, matrix tasks, artifacts, provider status, release config, changesets, changelog categories, targets, and release backends. Covers schema/ci.cue and schema/release.cue.
Use for cuenv services, readiness checks, service lifecycle commands, image definitions, image output refs, Nix/devenv/container/Dagger/OCI runtimes, and runtime status. Covers schema/services.cue, schema/images.cue, schema/runtime.cue, and schema/devenv.cue.
Use for any cuenv question, code change, documentation change, prompt update, or feature explanation where the answer must be grounded in the current CUE schema. Start here before using other cuenv skills.
| name | cuenv-tools-lock-vcs |
| description | Use for cuenv tools runtime, tool sources, platform overrides, extraction behavior, activation, lock sync, and VCS dependencies. Covers schema/tools.cue and schema/vcs.cue. |
Read docs/design/specs/schema-coverage-matrix.md, then inspect:
schema/tools.cue for #ToolsRuntime, #Tool, overrides, source unions, extracts, and activation.schema/vcs.cue for VCS dependency definitions.crates/tools/runtime/src/activation.rs for activation schema/mutation rules and crates/tools/runtime/src/activation/path_index.rs for lockfile provider path discovery.crates/cuenv/src/commands/tools.rs and sync providers when behavior matters.crates/cuenv/src/commands/sync/providers/vcs.rs for VCS sync orchestration, crates/cuenv/src/commands/sync/providers/vcs/materialization.rs for checkout and marker verification, crates/cuenv/src/commands/sync/providers/vcs/paths.rs for path/temp safety, and crates/cuenv/src/commands/sync/providers/vcs/git.rs for git subprocess execution.crates/ci/src/executor/tools.rs for CI task tool downloads and lockfile activation.crates/tools/github/src/lib.rs for GitHub release API resolution, asset selection, downloads, and cache target planning; crates/tools/github/src/extract.rs for archive extraction behavior.crates/tools/url/src/lib.rs for URL resolution/cache placement and crates/tools/url/src/extract.rs for URL archive extraction behavior.crates/tools/oci/src/provider.rs for registry/manifest/cache orchestration and crates/tools/oci/src/extract.rs for single-binary extraction from image layers.Status guardrails:
crates/tools/oci) extracts a single binary at path from the platform-specific manifest layers; image and path both honor {version}, {os}, and {arch} templates. Multi-arch image indexes are walked and the matching os/architecture entry is selected.crates/cuenv/src/commands/sync/providers/lock/tool_resolution.rs owns the literal {version}, {os}, and {arch} placeholders as constants; keep it warning-free without formatting-lint suppressions..zip, .tar.gz/.tgz, and .tar.xz/.txz. GitHub additionally extracts .pkg on macOS. Unknown extensions are treated as raw binaries — point users at a supported archive form rather than letting compressed bytes get written to disk.crates/tools/github/src/tests.rs and OCI GHCR auth tests in crates/tools/oci/src/registry.rs should use scoped temp_env overrides for GITHUB_TOKEN / GH_TOKEN, not unsafe process-wide environment mutation.crates/cuenv/tests/node_tool_integration.rs should stay network-free by locking official archive URLs, seeding fake URL-tool cache prefixes, and returning Result from fixture setup instead of reintroducing file-level unwrap/expect allowances.cuenv sync vcs for VCS dependencies.cuenv tools activate for lockfile activation metadata.#VcsDependency.subdir performs sparse-checkout of a single subtree. The lockfile records the subtree hash and re-syncs are deterministic; vendor: false ignores the materialized subtree instead of leaving a nested .git checkout.#VcsDependency.overlay: true requires subdir and vendor: false, then materializes each immediate directory child under path with per-child ownership markers and gitignore entries. Use it when repo-local siblings must live alongside synced children; invalid child names, loose files, submodules, symlinked overlay parents, and unmanaged child collisions are rejected before install.crates/cuenv/tests/vcs_subdir_e2e.rs network-free by seeding a local git source repo from the checkout's .agents/skills, rewriting examples/vcs-subdir/env.cue to that local remote, and returning Result from temp repo setup, recursive copy, git, and cuenv command execution instead of file-level unwrap/expect allowances.Adversarial prompts:
source: #Oci & {image: "...", path: "/usr/bin/tool"}. Confirm the image is multi-arch with entries for every platform in platforms; otherwise pair with #Override for platform-specific sources.#Override and #GitHubExtract.schema.#VcsDependency and cuenv sync vcs.subdir; cuenv runs a sparse-checkout and lands only that subtree at path..agents/skills while keeping local skills." Use subdir with overlay: true and vendor: false; cuenv manages each upstream child individually and leaves repo-local siblings alone.