Use GitHits package intelligence before making dependency claims from memory.

CLI Invocation

Run commands as githits ....
If githits is not found, retry the same command as npx -y githits@latest ....
Keep default text for model-read summaries, comparisons, and counts. Use --json only when code consumes the raw response or text omits a required field.
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.
If a command returns TERMS_ACCEPTANCE_REQUIRED, run githits settings terms accept or use the returned authenticated acceptance URL, then retry once.

Package Spec

Most package commands use <registry>:<name>[@<version>], for example npm:lodash@4.17.20 or pypi:requests.
pkg info always reports the latest published version and does not accept a version pin.
pkg changelog is package-only. Pin @version for one release; use @from..to or --from/--to for ranges. Repository and site targets are rejected.