githits 0.17.1 → 0.19.0

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "githits",
-  "version": "0.17.1",
+  "version": "0.19.0",
   "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.17.1",
+  "version": "0.19.0",
   "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.17.1",
+  "version": "0.19.0",
   "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.17.1",
+  "version": "0.19.0",
   "remotes": [
     {
       "type": "streamable-http",
@@ -28,7 +28,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "githits",
-      "version": "0.17.1",
+      "version": "0.19.0",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skills/githits-code/SKILL.md

@@ -21,9 +21,8 @@ Use GitHits for evidence from real open-source code instead of guessing from mod
 
 ## 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 a canonical cross-project example or pattern: `githits example "<focused question>"`; include source repositories/citations from GitHits' generated references/provenance section. If GitHits cannot match `--lang`, retry with a suggested language from the error, or omit `--lang`.
 - 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 public repository: 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`.
@@ -35,7 +34,6 @@ Use GitHits for evidence from real open-source code instead of guessing from mod
 ```bash
 githits example "how to use express middleware"
 githits example "react hooks patterns" --lang typescript
-githits languages type
 
 githits search "router middleware" --in npm:express@5.2.1
 githits search "debounce" --in npm:lodash@4.18.1 --source symbol

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

@@ -1,6 +1,6 @@
 # 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. Package targets inspect an indexed artifact/manifest root. Swift package targets use `swift:github.com/<owner>/<repo>` and Zig package targets use `zig:gh/<owner>/<repo>`. Use public repository targets for full repositories or sibling packages. Repository compact targets use `github:org/repo[#ref|@ref]`, `codeberg:owner/repo[#ref|@ref]`, `gitlab:group[/subgroup...]/project[#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 `provider:path#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. Package targets inspect an indexed artifact/manifest root. Swift package targets use `swift:github.com/<owner>/<repo>` and Zig package targets use `zig:gh/<owner>/<repo>`. Use public repository targets for full repositories or sibling packages. Repository compact targets use `github:org/repo[@ref]`, `codeberg:owner/repo[@ref]`, `gitlab:group[/subgroup...]/project[@ref]`, `github.com/org/repo[@ref]`, or `https://github.com/org/repo[@ref]`; omitted refs request the backend default-branch intent. Exact standalone documentation sites use `site:<host[/path]>`. Output uses canonical `provider:path@ref` formatting so refs can contain `@` safely. `code` commands also support `--repo-url <url> [--git-ref <ref>]`.
 
 ## Search
 
@@ -57,15 +57,14 @@ Partial and capped documentation coverage are usable published evidence. Report
 ## Command Name Mapping
 
 - `githits example` maps to MCP `get_example`.
-- `githits languages` maps to MCP `search_language`.
 - `githits search` maps to MCP `search`.
 - `githits search-status` maps to MCP `search_status`.
 - `githits code files` maps to MCP `code_files`.
 - `githits code grep` maps to MCP `code_grep`.
-- `githits code read` maps to MCP `code_read`.
+- `githits code read` maps to MCP `read` with `target` and `path`.
 - `githits docs list` maps to MCP `docs_list`.
-- `githits docs read` maps to MCP `docs_read`.
+- `githits docs read` maps to MCP `read` with `target` alone.
 
-Direct repository targets accept approved full HTTPS URLs on github.com, codeberg.org, and gitlab.com. Codeberg requires exactly owner/repo; GitLab allows nested namespaces. Only GitHub supports host shorthand and HTTP compatibility. Never infer a provider from bare owner/repo. Refs may contain / and @ after # or @; empty refs and mixed suffixes are invalid. Credentials, queries, provider web subpaths, and unsupported/self-hosted hosts are rejected. Package targets keep registry-native coordinates, including `zig:cb/owner/repo` and `swift:gitlab.com/group/project`. Changelog repo URL fields remain full HTTPS URLs.
+Direct repository targets accept approved full HTTPS URLs on github.com, codeberg.org, and gitlab.com. Codeberg requires exactly owner/repo; GitLab allows nested namespaces. Only GitHub supports host shorthand and HTTP compatibility. Never infer a provider from bare owner/repo. Repository refs use an @ suffix and may themselves contain / and @; # is reserved for semantic fragments. Empty refs and mixed suffixes are invalid. Credentials, queries, provider web subpaths, and unsupported/self-hosted hosts are rejected. Package targets keep registry-native coordinates, including `zig:cb/owner/repo` and `swift:gitlab.com/group/project`. Changelog repo URL fields remain full HTTPS URLs.
 
 GitLab web paths with `/-/` or reserved routes such as `tree`, `blob`, and `raw` are rejected. Unreserved names such as `issues` can be repository path components; without a web-route marker, the client treats the complete nested path as repository identity.

package/skills/githits-mcp/SKILL.md

@@ -32,14 +32,16 @@ the routing decision; the selected tool supplies its argument details.
 | Find canonical implementation examples across projects | `get_example` |
 | Check progress of an earlier search reference | `search_status` |
 
-Use `search_language` only if `get_example` needs language disambiguation. For comparative questions, combine
+If `get_example` cannot match a language, retry with a suggested language from the error, or omit language. For comparative questions, combine
 the relevant package/source route with examples when needed.
 
 Scope: public OSS only, never local/private/proprietary source. Package targets
 use `registry:name[@version]` and inspect an indexed artifact/manifest root;
 Swift uses `swift:github.com/<owner>/<repo>`, Zig `zig:gh/<owner>/<repo>`.
 Use public repository targets for full repositories or sibling packages, with
-an explicit provider (such as `github:owner/repo`) or supported full URL.
+an explicit `github:`, `codeberg:`, or `gitlab:` provider, or a supported full URL.
+Append revisions as `@ref`; refs may contain later `@` characters. `#` is
+reserved for semantic fragments and never identifies a repository revision.
 Never infer a repository provider. Use selected tool descriptions for supported
 target forms and argument details.