envit

name	envit
description	How to use envit, the repo-context tool — it materializes the source code of a project's dependencies into .envit/repos/ so you can read real library source instead of guessing. Use this skill whenever you see an envit.json or .envit/ directory in a project, whenever you need to read the source of a dependency or open-source library, whenever library context seems missing or stale, or whenever the user mentions envit, repo context, or asks you to add/pin/update a context repo.
license	MIT OR Apache-2.0

envit — repo context for agents

envit is a virtualenv for repo context. The project's envit.json declares which git repositories an agent should be able to read; envit sync materializes them, read-only and commit-pinned, under .envit/repos/. The bytes live once per machine in a shared store — never edit them, and never commit .envit/ (it's gitignored; the manifest and envit.lock.json are committed instead).

Reading context (the common case — no commands needed)

1. Read .envit/AGENTS.md first: it lists every available repo, its commit, and its resolved path.
2. Dependency source lives at .envit/repos/<name>/ — real, complete, at the exact commit the lockfile pins. Prefer reading it over guessing at a library's behavior from memory.
3. The entries are symlinks: rg and fd skip them by default. Use rg --follow / fd -L, or search the resolved store path from AGENTS.md (generated) directly.
4. Everything is read-only by design. If you need to modify a dependency, that's a fork/vendor decision for the user — say so instead of fighting the permissions.