githits 0.6.2 → 0.6.4

package/gemini-extension.json

@@ -1,7 +1,7 @@
 {
   "name": "githits",
-  "version": "0.6.2",
-  "description": "Code examples from global open source for developers and AI assistants.",
+  "version": "0.6.4",
+  "description": "The code context layer for AI coding agents",
   "mcpServers": {
     "githits": {
       "command": "npx",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "githits",
-  "description": "Version-aware open-source context for agentic software development",
-  "version": "0.6.2",
+  "description": "The code context layer for AI coding agents",
+  "version": "0.6.4",
   "mcpName": "com.githits/githits",
   "type": "module",
   "workspaces": [
@@ -39,7 +39,10 @@
     "dev": "bun run ./src/cli.ts",
     "inspector": "npx @modelcontextprotocol/inspector bun run dev mcp",
     "smoke:cli": "bun run scripts/cli-smoke.ts",
+    "smoke:cli:built": "bun run scripts/cli-smoke.ts --mode unauthenticated --cli-entry dist/cli.js",
     "smoke:mcp": "bun run scripts/mcp-smoke.ts",
+    "smoke:mcp:built": "bun run scripts/mcp-smoke.ts --mode registration --cli-entry dist/cli.js",
+    "smoke:proxy-node": "bun run scripts/run-proxy-node-smoke.ts",
     "validate:packages": "bun run scripts/validate-public-packages.ts",
     "validate:packages:mcp-publish": "bun run scripts/validate-public-packages.ts --mcp-publish-dry-run",
     "sync:claude-skills": "bun run scripts/sync-claude-skill-assets.ts",
@@ -79,7 +82,7 @@
     "url": "https://github.com/githits-com/githits-cli/issues"
   },
   "engines": {
-    "node": "^20.12.0 || >=22.13.0"
+    "node": "^20.18.1 || >=22.13.0"
   },
   "publishConfig": {
     "access": "public"
@@ -96,6 +99,7 @@
     "open": "^11.0.0",
     "semver": "7.8.5",
     "smol-toml": "^1.6.1",
+    "undici": "7.28.0",
     "yaml": "^2.9.0",
     "zod": "^4.4.3"
   },

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "githits",
-  "version": "0.6.2",
-  "description": "Code examples from global open source for developers and AI assistants",
+  "version": "0.6.4",
+  "description": "The code context layer for AI coding agents",
   "author": {
     "name": "GitHits"
   },

package/plugins/claude/skills/githits-mcp/SKILL.md

@@ -22,6 +22,8 @@ Use the most targeted GitHits MCP tool or combination of tools for the job:
 - 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.
 
+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.
 
 ## External Content Posture

package/plugins/claude/skills/search/SKILL.md

@@ -36,6 +36,8 @@ Guidelines:
 - When the task is about indexed dependency or repository internals, prefer
   unified `search` instead of
   `get_example`.
+- Prefer the default compact text output. Request JSON only when exact
+  structured fields are necessary.
 - After using results, send `feedback` with helpful/unhelpful outcome.
 
 Tool argument details and rich query guidance are provided directly in the MCP

package/server.json

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

package/skills/githits-mcp/SKILL.md

@@ -22,6 +22,8 @@ Use the most targeted GitHits MCP tool or combination of tools for the job:
 - 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.
 
+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.
 
 ## External Content Posture

package/dist/shared/chunk-572afq8h.js

@@ -1,2 +0,0 @@
-import{createRequire}from"node:module";var __require=createRequire(import.meta.url);var version="0.6.2";
-export{__require,version};