Pin npm, cargo, and git sources into read-only grepo alias trees.
npx skills add https://github.com/tomrford/config --skill grepo
Please help me install this Agent Skill. Skill: grepo Source: https://github.com/tomrford/config/tree/main/.agents/skills/grepo Command: npx skills add https://github.com/tomrford/config --skill grepo
grepo pins recurring read-only reference sources into a project-local grepo/ directory. grepo/.lock is the tracked source of truth; each grepo/<alias> is a generated symlink into a shared cached snapshot (a read-only tree with .git stripped).
Initialize grepo in your project, add references with grepo add, then run grepo sync or grepo update to materialize and refresh snapshots.
High-intent search queries and answers about installing and using this skill.
Project-local reference snapshots are managed by pinning external sources into read-only trees under a grepo directory. A lockfile acts as the source of truth, symlinking aliases to cached snapshots to ensure deterministic builds across the workspace.
Pinning npm packages and cargo crates is handled by adding sources to a lockfile and materializing them as read-only alias trees. Using a sync command applies lockfile pins while an update command advances movable entries for deterministic version control.
A lockfile-driven snapshot reduces drift by serving as a tracked single source of truth for all reference sources. Each developer runs a sync command to materialize identical read-only trees via symlinks from a shared central cache, ensuring reproducible environments.
Git URLs can be used as reference sources with subdir and ref handling. The system pins specific commits and materializes the repository contents into read-only alias trees, stripping the .git directory to create stable project-local snapshots.
Alias trees must be read-only to prevent accidental modifications to the materialized snapshots. This ensures the cached external sources remain stable and reproducible across the workspace, allowing reliable deterministic updates driven solely by the lockfile.
You need a project with a grepo/.lock file to initialize reference management. This lockfile is the tracked source of truth that records all alias trees, package sources, and commit pins required to control exactly what is materialized.
tomrfordDelegate repo-grounded research tasks to a subagent analyzing grepo snapshots.
SakshamKandelDisplay a read-only dashboard of version slots and imminent workspace shippings.
sgcarstrendsManage pnpm workspaces and cross-package dependencies across monorepo packages.
kanyun-incManage AI agent skills with a Git-based package manager.
