prompts/skills/local-git-reference/SKILL.md
Use when looking up project docs, source, examples, specs, or upstream context, and extra/ does not contain what you need. Check ~/src first, clone relevant repos with ghq, and prefer local inspection/search over remote browsing.
npx skillsauth add ramblurr/nix-devenv local-git-referenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
~/src is the human (and your) personal library of useful git repositories.
Use it for any git repo that may contain information relevant to the task, not just code repositories. That includes docs repos, examples, specs, infra repos, deployment repos, and companion repos related to a project.
Be proactive. If a project, tool, library, or service seems relevant, look for likely repos and clone them into ~/src so you can inspect and search them locally.
Related skills: extra-reference-material for material in extra/
~/src for a relevant repo first.ghq clone.git pull inside the repo before relying on it.The docs repo may be different from the main code repo. If a docs site or project appears relevant, proactively look for related git repos and clone them too.
Clone a repo into ~/src:
ghq clone https://github.com/owner/repo.git
Clone a likely companion repo too when useful:
ghq clone https://github.com/owner/project-docs.git
Refresh a local clone when freshness matters:
cd ~/src/github.com/owner/repo && git pull --ff-only
Use the bundled scripts to search ~/src without dumping unbounded output into context.
scripts/find-repos.sh: find candidate repositories by path or repo namescripts/search-src.sh: search file contents under ~/srcBoth scripts:
Examples:
scripts/find-repos.sh caddy
scripts/search-src.sh 'reverse_proxy'
Increase the display cap deliberately when needed:
scripts/search-src.sh --max-results 80 'tls internal'
Prioritize the files most likely to answer the question:
README*docs/examples/Use local repo contents as primary reference material whenever practical.
Err on cloning a relevant remote repo if it is not already present in ~/src. Local searchable checkouts are often faster and more useful than repeated remote browsing.
testing
Use this OCP when executing or preparing to execute commands that change a live or important system, service reloads/restarts, package changes, deployments, migrations, firewall/network/access changes, credential rotation, NixOS switch/test/boot/deploy, or incident mitigation. It guides safe operations with a persisted ledger for scope, preflight, baseline, rollback, validation, and evidence.
development
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
documentation
Naming conventions for workflow documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs or research reports, (3) questions about document organization in prompts/.
testing
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.