Use GitHits for evidence from real open-source code instead of guessing from model memory.

CLI Invocation

Run commands as githits ....
If githits is not found, retry the same command as npx -y githits@latest ....
Use --json when you need stable fields to parse or chain into another command.
Do not expose credentials. If auth is required interactively, run githits login; use githits login --no-browser only when the user can complete the printed URL flow. In noninteractive eval/CI, do not start OAuth; report that GITHITS_API_TOKEN or prior login is required.

Decision Flow

Need a canonical cross-project example or pattern: githits example "<focused question>"; include source repositories/citations from GitHits' generated references/provenance section whenever present.
Need package metadata, vulnerability/advisory status, dependency graphs, or release notes: stop and use the githits-package skill instead.
Exact language name uncertain for example --lang: run githits languages <query> first.
Inspecting a known dependency or GitHub repo: start with githits search scoped by --in.
Need file/path enumeration: use githits code files; do not probe directories with code read.
Know the exact text or regex to match: use githits code grep; use githits search for discovery.
Need documentation pages: use githits search "<topic>" --source docs --in <target> for topic search, or githits docs list <spec> to browse available pages.