githits 0.9.2 → 0.9.3

package/dist/shared/{chunk-dqq6yv70.js → chunk-g3jtxnfk.js}

@@ -1,2 +1,2 @@
-import{createRequire}from"node:module";var __require=createRequire(import.meta.url);var description="The code context layer for AI coding agents";var version="0.9.2";
+import{createRequire}from"node:module";var __require=createRequire(import.meta.url);var description="The code context layer for AI coding agents";var version="0.9.3";
 export{__require,description,version};

package/dist/shared/{chunk-9wrnhdst.js → chunk-kc1y3rd7.js}

@@ -1 +1 @@
-import{clearAutoLoginAuthSessionMetadata,createAuthCommandDependencies,createAuthStatusDependencies,createContainer,loadAutoLoginAuthSessionMetadata,recordAuthFingerprint}from"./chunk-89dydy8a.js";import"./chunk-dqq6yv70.js";export{recordAuthFingerprint,loadAutoLoginAuthSessionMetadata,createContainer,createAuthStatusDependencies,createAuthCommandDependencies,clearAutoLoginAuthSessionMetadata};
+import{clearAutoLoginAuthSessionMetadata,createAuthCommandDependencies,createAuthStatusDependencies,createContainer,loadAutoLoginAuthSessionMetadata,recordAuthFingerprint}from"./chunk-etx8jndp.js";import"./chunk-g3jtxnfk.js";export{recordAuthFingerprint,loadAutoLoginAuthSessionMetadata,createContainer,createAuthStatusDependencies,createAuthCommandDependencies,clearAutoLoginAuthSessionMetadata};

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "The code context layer for AI coding agents",
   "mcpServers": {
     "githits": {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "githits",
   "description": "The code context layer for AI coding agents",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "mcpName": "com.githits/githits",
   "type": "module",
   "workspaces": [

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "githits",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"

package/server.json

@@ -16,7 +16,7 @@
     "source": "github",
     "id": "1165453165"
   },
-  "version": "0.9.2",
+  "version": "0.9.3",
   "remotes": [
     {
       "type": "streamable-http",
@@ -28,7 +28,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "githits",
-      "version": "0.9.2",
+      "version": "0.9.3",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skills/githits-code/SKILL.md

@@ -24,6 +24,7 @@ Use GitHits for evidence from real open-source code instead of guessing from mod
 - 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`.
+- Searching an exact standalone documentation site: use `githits search "<topic>" --source docs --in site:<host[/path]>`. If the result reports suggested site targets, retry one explicitly; suggestions are advisory targets, not aliases.
 - Need file/path enumeration: use `githits code files`; do not probe directories with `code read`.
 - Know the exact text to match: use `githits code grep` (literal by default). Pass `--regex` for RE2 syntax; lookaround and backreferences are unsupported. 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.
@@ -38,6 +39,7 @@ githits languages type
 githits search "router middleware" --in npm:express@5.2.1
 githits search "debounce" --in npm:lodash@4.18.1 --source symbol
 githits search '"body parser" OR multer' --in npm:express --source docs --json
+githits search "middleware" --in site:expressjs.com --source docs
 githits search-status <searchRef>
 
 githits code files npm:express@5.2.1 lib/ --ext js --limit 100
@@ -55,12 +57,13 @@ githits docs read <pageId> --lines 20-120
 - For `githits example` results, report the source repositories/citations shown in GitHits' generated references/provenance section; they are core evidence for the synthesized pattern.
 - Package targets inspect published artifacts and omitted versions resolve to the latest release; repository targets inspect repository trees. For source-layout questions, always pin and report the package version or Git ref.
 - For source work, locate symbols or matches first, then read a focused window with explicit `--lines`.
-- Documentation text reads return at most 150 lines per call. Continue with the reported returned range and `totalLines` when more context is needed.
+- Documentation text reads return at most 150 lines per call. Continue with explicit `--lines` windows when more context is needed; pass `--json` when you need `startLine`, `endLine`, or `totalLines` pagination metadata.
 - For multi-step code/docs investigations, keep raw CLI output out of the final answer unless it is the evidence the user needs.
 - If output says it used recent/stale indexed evidence, treat the displayed served target as provenance; if freshness matters, retry with a longer `--wait` or use one of the displayed `queryable now` versions/refs, or inspect JSON `targetResolution` for structured candidates.
 - Treat partial documentation coverage as incomplete evidence and retry later when advised. Capped coverage is terminal for the current crawl, so report the limitation instead of retrying.
 - If search returns a `searchRef`, continue with `githits search-status <searchRef>` instead of repeating the original search. Its bounded wait defaults to 20 seconds; use `--wait <seconds>` with an integer from 0 to 60 to adjust it.
 - If grep returns no matches, do not repeat it unchanged. Follow the returned guidance by changing the pattern, broadening the file scope, or switching to `githits search` for conceptual discovery.
+- For a missing or ambiguous standalone site, use the returned `suggestedSiteTargets` in order. Do not rewrite the original target or retry automatically; when `suggestedSiteTargetsTruncated` is true, state that additional candidates were omitted.
 - If a code-navigation command returns `INDEXING`, use the elapsed/expected duration in the message to decide whether to retry with `--wait`; prefer any displayed indexed refs/versions when you need an immediate follow-up.
 - After using GitHits results, send feedback when practical. Use `githits feedback <solution_id> --accept|--reject` for `githits example` results, or omit `<solution_id>` for generic session feedback such as `githits feedback --reject --tool search -m "missing kotlin support"`.
 

package/skills/githits-code/references/code-and-docs.md

@@ -1,15 +1,17 @@
 # GitHits Code And Docs CLI Reference
 
-Package target syntax requires an explicit registry: `registry:name[@version]`, for example `npm:express@5.2.1`; omit `@version` for the latest release. Repository compact targets use `github:org/repo[#ref|@ref]`, `github.com/org/repo[#ref|@ref]`, or `https://github.com/org/repo[#ref|@ref]`; omitted refs request the backend default-branch intent. Output uses canonical `github:org/repo#ref` formatting so refs can contain `@` safely. `code` commands also support `--repo-url <url> [--git-ref <ref>]`.
+Package target syntax requires an explicit registry: `registry:name[@version]`, for example `npm:express@5.2.1`; omit `@version` for the latest release. Repository compact targets use `github:org/repo[#ref|@ref]`, `github.com/org/repo[#ref|@ref]`, or `https://github.com/org/repo[#ref|@ref]`; omitted refs request the backend default-branch intent. Exact standalone documentation sites use `site:<host[/path]>`. Output uses canonical `github:org/repo#ref` formatting so refs can contain `@` safely. `code` commands also support `--repo-url <url> [--git-ref <ref>]`.
 
 ## Search
 
-`githits search "<query>" --in <target>` searches indexed dependency code, docs, and symbols. Repeat `--in` for multiple targets. Use `--source code`, `--source docs`, or `--source symbol` to force a source; omit it for auto-routing.
+`githits search "<query>" --in <target>` searches indexed dependency code, docs, symbols, and exact standalone documentation sites. Repeat `--in` for multiple targets. Use `--source code`, `--source docs`, or `--source symbol` to force a source; omit it for auto-routing. For a standalone site, pass `--source docs --in site:<host[/path]>`.
 
 Useful filters: `--kind`, `--category`, `--path-prefix`, `--intent`, `--public`, `--name`, `--lang`, `--limit`, `--offset`, `--wait`, `--allow-partial`, `--json`.
 
 If search returns a `searchRef`, do not repeat the original search. Continue with `githits search-status <searchRef> [--wait <seconds>]`; the bounded wait defaults to 20 seconds, and the explicit value must be an integer from 0 to 60.
 
+If a missing or ambiguous site returns suggested site targets, retry one of those exact labels explicitly. They are advisory, not aliases, and GitHits does not select or retry one automatically. A truncation notice means more valid candidates were omitted.
+
 ## Code Files
 
 `githits code files <spec> [path-prefix]` lists paths. Use this before `code read` when you do not know the exact file path.
@@ -33,7 +35,7 @@ When grep returns no matches, do not repeat it unchanged. Change or shorten the
 
 `githits docs list <spec>` browses available documentation pages. It is not topic search.
 
-`githits docs read <pageId>` reads a page. Text output returns at most 150 lines per call, including larger explicit ranges; continue from the reported returned range when more context is needed. Use `--lines` for bounded windows and `--json` when extracting `totalLines` or source metadata.
+`githits docs read <pageId>` reads a page. Text output returns at most 150 lines per call, including larger explicit ranges; continue with explicit `--lines` windows when more context is needed. Use `--json` when extracting `startLine`, `endLine`, `totalLines`, or source metadata.
 
 For topic search, use `githits search "<topic>" --source docs --in <target>`, then pass the returned page ID to `docs read`.
 

package/skills/githits-mcp/SKILL.md

@@ -18,10 +18,13 @@ Scope boundaries:
 Use the most targeted GitHits MCP tool or combination of tools for the job:
 
 - Use `search` and `docs_*` for package documentation, repository docs, exact APIs, configuration, or setup behavior.
+- For an exact standalone documentation site, call `search` with target `site:<host[/path]>` and source `docs`. Follow a returned `searchRef` with `search_status`; if a missing or ambiguous site instead returns `suggestedSiteTargets`, retry one exact suggestion explicitly rather than rewriting the target or treating it as an alias.
 - Use `search`, `code_files`, `code_grep`, and `code_read` for version-specific package/repository source, tests, symbols, call sites, and implementation evidence.
 - Use `pkg_info`, `pkg_vulns`, `pkg_deps`, `pkg_changelog`, and `pkg_upgrade_review` for package metadata, versions, adoption, vulnerabilities, dependency graphs, changelogs, and upgrade-review evidence.
 - Use `get_example` as the broad OSS-first discovery, planning, and research path for vague issues, unfamiliar errors, "how do others do this" questions, multi-library/API combinations, global implementation-pattern scans, and rare needle-in-the-haystack examples that may appear in only one or a few repositories. When the dependency or repository is already known, default to `search`, `docs_*`, and `code_*` first; add `get_example` when you need broader cross-project evidence or a hard-to-find real-world example.
 
+If GitHits MCP tools are unavailable but the `githits` CLI is installed, switch to the `githits-code` or `githits-package` skill and use its equivalent CLI commands. Do not treat missing MCP registration as evidence that GitHits lacks the requested content.
+
 Prefer the default compact text output. Request JSON only when exact structured fields are necessary.
 
 When answering, ground claims in fetched GitHits evidence and cite the relevant package, repository, file, docs page, or version facts when available. If GitHits does not have enough evidence, say what is missing and then use the next best source.