hermit-tooling
Skill57 starsChanged 44 days agoApache-2.0View on GitHub
Diagnose missing developer tools or Hermit activation failures in this repository.
Files
Tool availability
Determine whether this checkout is using Hermit or the supported non-Hermit setup in CONTRIBUTING.md.
For Hermit, activate with source bin/activate-hermit from the repo root and
check the required tool with command -v. The committed proxies are under
bin/; they resolve packages through Hermit, not a universal .hermit/ bin
directory. Inspect bin/hermit.hcl and the actual proxy when resolution fails.
Distinguish missing packages from activation, cache-permission, and network
errors. Do not install global replacements to hide a Hermit failure. If
lefthook is unavailable, restore the toolchain and run just install-hooks;
do not bypass hooks. For non-Hermit setups, use the documented prerequisites.
Report unresolved setup blockers without claiming that validation ran.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- client/AGENTS.mdAGENTS.md
- proto/AGENTS.mdAGENTS.md
- server/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- asicrs-buildSkill
- code-generationSkill
- docker-compose-devSkill
- fake-rig-fixturesSkill
- migration-immutabilitySkill
- planSkill
- plugin-contract-testsSkill
- pr-describeSkill
- proto-fleet-playwright-e2eSkill
- pr-readySkill
- python-gen-tarballSkill
- regenSkill
- release-notesSkill
- triage-prSkill
- code-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.